aboutsummaryrefslogtreecommitdiff
path: root/src/interfaces
Commit message (Collapse)AuthorAge
* here are the patches for psql on Win32:Bruce Momjian2003-07-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | psql4win32.patch - changes in the psql source code psql-ref.patch - changes in the documentation psql-ref.sgml (for new builtin variable WIN32_CONSOLE) To apply them use "patch -p 1" in the root directory of the postgres source directory. These patches fix the following problems of psql on Win32 (all changes only have effect #ifdef WIN32): a) Problem: Static library libpq.a did not work Solution: Added WSAStartup() in fe-connect.c b) Problem: Secret Password was echoed by psql Solution: Password echoing disabled in sprompt.c c) Problem: 8bit characters were displayed/interpreted wrong in psql This is due to the fact that the Win32 "console" uses a different encoding than the rest of the Windows system Solution: Introduced a new psql variable WIN32_CONSOLE When set with "\set WIN32_console", the function OemToChar() is applied after reading input and CharToOem() before displaying Output Christoph Dalitz
* At long last I put together a patch to support 4 client SSL negotiationBruce Momjian2003-07-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | modes (and replace the requiressl boolean). The four options were first spelled out by Magnus Hagander <mha@sollentuna.net> on 2000-08-23 in email to pgsql-hackers, archived here: http://archives.postgresql.org/pgsql-hackers/2000-08/msg00639.php My original less-flexible patch and the ensuing thread are archived at: http://dbforums.com/t623845.html Attached is a new patch, including documentation. To sum up, there's a new client parameter "sslmode" and environment variable "PGSSLMODE", with these options: sslmode description ------- ----------- disable Unencrypted non-SSL only allow Negotiate, prefer non-SSL prefer Negotiate, prefer SSL (default) require Require SSL The only change to the server is a new pg_hba.conf line type, "hostnossl", for specifying connections that are not allowed to use SSL (for example, to prevent servers on a local network from accidentally using SSL and wasting cycles). Thus the 3 pg_hba.conf line types are: pg_hba.conf line types ---------------------- host applies to either SSL or regular connections hostssl applies only to SSL connections hostnossl applies only to regular connections These client and server options, the postgresql.conf ssl = false option, and finally the possibility of compiling with no SSL support at all, make quite a range of combinations to test. I threw together a test script to try many of them out. It's in a separate tarball with its config files, a patch to psql so it'll announce SSL connections even in absence of a tty, and the test output. The test is especially informative when run on the same tty the postmaster was started on, so the FATAL: errors during negotiation are interleaved with the psql client output. I saw Tom write that new submissions for 7.4 have to be in before midnight local time, and since I'm on the east coast in the US, this just makes it in before the bell. :) Jon Jensen
* Added explicit casts for date/interval/timestamp.Michael Meskes2003-07-25
|
* Applied Peter's patch to use yyless instead of my string_unput function.Michael Meskes2003-07-25
|
* Fixed mdy functions to use correct offset.Michael Meskes2003-07-24
|
* Fixes additional sql injection vulnerabilities reported by Oliver JowettBarry Lind2003-07-24
| | | | | | | | and Dmitry Tkach. Specifically the previous fix still allowed the statement termination character through in unquoted places in the sql statement, and the driver never correctly handled someone passing a value of \0 in a string which under the v2 protocol would end the statement causing the following text to possibly be treated as a new sql statement Modified Files: jdbc/org/postgresql/Driver.java.in jdbc/org/postgresql/jdbc1/AbstractJdbc1Statement.java
* Have a go at fixing various outstanding portability issues in code thatTom Lane2003-07-23
| | | | | | | | | was modified for IPv6. Use a robust definition of struct sockaddr_storage, do a proper configure test to see if ss_len exists, don't assume that getnameinfo() will handle AF_UNIX sockets, don't trust getaddrinfo to return the protocol we ask for, etc. This incorporates several outstanding patches from Kurt Roeckx, but I'm to blame for anything that doesn't work ...
* Czech translation updates from Karel ZakPeter Eisentraut2003-07-23
|
* Fix to prevent SQL injection attacks for code calling setObject(int,Object,int)Barry Lind2003-07-22
| | | | | | | | | | where Object is a user supplied String and the type is a numeric type (i.e. INTEGER,LONG,etc). Also applied a patch from Kim Ho that fixes compile problems under jdk1.2 Modified Files: jdbc/org/postgresql/Driver.java.in jdbc/org/postgresql/jdbc1/AbstractJdbc1Statement.java
* Applied patch from dmitry@openratings.com to fix parsing of array valuesBarry Lind2003-07-21
| | | | | | Modified Files: jdbc/org/postgresql/Driver.java.in jdbc/org/postgresql/jdbc2/Array.java
* Added more compat stuff ot the parser.Michael Meskes2003-07-18
|
* Add an upper limit to IS_VALID_JULIAN() to defend against overflow inTom Lane2003-07-17
| | | | | date2j(). This ensures we give reasonable errors instead of bizarre behavior for input dates far in the future.
* Allow blanks at the end of numerical values.Michael Meskes2003-07-17
|
* Fixed some bugs in Informix compat functions.Michael Meskes2003-07-17
|
* Make EXTRACT(TIMEZONE) and SET/SHOW TIMEZONE follow the SQL conventionTom Lane2003-07-17
| | | | | | for the sign of timezone offsets, ie, positive is east from UTC. These were previously out of step with other operations that accept or show timezones, such as I/O of timestamptz values.
* Applied patch to fix two compatibility functions.Michael Meskes2003-07-16
|
* Started to create different error codes for different backend messages.Michael Meskes2003-07-15
|
* Missed one rule in syncinc preproc.y which resulted in reduce/reduce conflicts.Michael Meskes2003-07-14
|
* - Synced preproc.y with gram.yMichael Meskes2003-07-14
| | | | | - Init sqlca in ECPGprepare(). - Added CLOSE DATABASE for Informix compatibility.
* Argh! Missed one file.Michael Meskes2003-07-09
|
* Fixed some Informix compat functions so they handle NULL resp. indicators ↵Michael Meskes2003-07-09
| | | | better.
* Applied patch from Kim Ho @ redhat.com to make support for setObject() moreBarry Lind2003-07-09
| | | | | | | | spec complient with regards to various data/time/timestamp objects Modified Files: jdbc/org/postgresql/errors.properties jdbc/org/postgresql/jdbc1/AbstractJdbc1Statement.java
* More informix fixes.Michael Meskes2003-07-08
|
* Fix segfault in connect in informix mode.Michael Meskes2003-07-08
|
* "char *" of course is not the same as "char []". So I had to fix the way ↵Michael Meskes2003-07-07
| | | | ecpg treated the second one.
* tm2timestamp should return -1, not elog, on overflow. (In the backendTom Lane2003-07-04
| | | | | this is merely an API inconsistency, but in ecpg it's fatal.) Also, fix misconceived overflow test in HAVE_INT64_TIMESTAMP case.
* Fix missing code for HAVE_INT64_TIMESTAMP.Tom Lane2003-07-04
|
* Add #include <limits.h> (re-add lost change from Wednesday).Tom Lane2003-07-04
|
* date, interval and timestamp data should be quoted.Michael Meskes2003-07-04
|
* Fixed informix behaviour for select without into.Michael Meskes2003-07-04
|
* Fixed initialization bug and added postgres_fe.h to pgtypeslib.Michael Meskes2003-07-02
|
* Fix ecpg typo --- change ;; to ;.Bruce Momjian2003-07-01
|
* Use ISO dates in pgtypeslib by default.Michael Meskes2003-07-01
| | | | | | | Applied patch by Philip Yarra to fix some thread issues. Added a new data type "decimal" which is mostly the same as our "numeric" but uses a fixed length array to store the digits. This is for compatibility with Informix and maybe others.
* patches by Kim Ho to fixDave Cramer2003-06-30
| | | | | | getByte, getSort if input has decimal or whitespace setObject if object is a BIT boolean not on list of SQLKeywords
* Patches applied:Barry Lind2003-06-30
| | | | | | | | | | | | | | | 1) Patch from Kris Jurka to fix IPv6 parsing of the jdbc URL 2) Patch from Kris Jurka to fix an ArrayIndexOutOfBounds error when calling moveToCurrentRow while currentRow is "beforeFirst" 3) Patch from Kim Ho to fix add some bounds checking in setMaxRows(), setQueryTimeout(), setFetchSize() Modified Files: jdbc/org/postgresql/Driver.java.in jdbc/org/postgresql/errors.properties jdbc/org/postgresql/jdbc1/AbstractJdbc1Statement.java jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java jdbc/org/postgresql/jdbc2/AbstractJdbc2Statement.java
* - Made sure Informix style decimal vars are initialized. They use aMichael Meskes2003-06-29
| | | | | | | fixed amount of digits and not an allocated one. So we have to work around. PostgreSQL numeric type remains the same. - In INFORMIX_SE mode with autcommit set, make all cursors be "with hold". Is this really they way SE behaves?
* Just another sync.Michael Meskes2003-06-29
|
* Merge PO file updates from 7.3 branch.Peter Eisentraut2003-06-28
|
* When using new protocol, PQexec can get out of a COPY IN or COPY OUTTom Lane2003-06-28
| | | | state by itself, so do so.
* Create real array comparison functions (that use the element datatype'sTom Lane2003-06-27
| | | | | | | | | | | | | | | | comparison functions), replacing the highly bogus bitwise array_eq. Create a btree index opclass for ANYARRAY --- it is now possible to create indexes on array columns. Arrange to cache the results of catalog lookups across multiple array operations, instead of repeating the lookups on every call. Add string_to_array and array_to_string functions. Remove singleton_array, array_accum, array_assign, and array_subscript functions, since these were for proof-of-concept and not intended to become supported functions. Minor adjustments to behavior in some corner cases with empty or zero-dimensional arrays. Joe Conway (with some editorializing by Tom Lane).
* Added just another compatibility level for Informix.Michael Meskes2003-06-26
|
* Wrap LONG_LONG_MIN redfinition around HAVE_LONG_LONG_INT_64.Bruce Momjian2003-06-26
|
* Fix compile problem for missing LONG_LONG_MIN on BSD/OS.Bruce Momjian2003-06-26
|
* Back out array mega-patch.Bruce Momjian2003-06-25
| | | | Joe Conway
* The remaining files ...Michael Meskes2003-06-25
|
* remove including of postgres_fe.hMichael Meskes2003-06-25
|
* Some systems need another header file included.Michael Meskes2003-06-25
|
* Implemented Informix special way to treat NULLs, removed warnings, synced.Michael Meskes2003-06-25
|
* > This change (I'm sure this will wrap poorly -- sorry):Bruce Momjian2003-06-25
| | | | | | | | | | | | | | | | | | | > http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/include/libpq/pqcomm.h.diff?r1=1.85&r2=1.86 > > modified SockAddr, but no corresponding change was made here > (fe-auth.c:612): > > case AUTH_REQ_KRB5: > #ifdef KRB5 > if (pg_krb5_sendauth(PQerrormsg, conn->sock, &conn->laddr.in, > &conn->raddr.in, > hostname) != STATUS_OK) > > It's not obvious to me what the change ought to be though. This patch should hopefully fix both kerberos 4 and 5. Kurt Roeckx
* This is a bug in python interface module,Bruce Momjian2003-06-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | postgresql-7.3.3/src/interfaces/python/pg.py. _quote() function fails due to integer overflow if input d is larger than max integer. In the case where the column type is "BIGINT", the input d may very well be larger than max integer while its type, t, is labeled 'int'. The conversion on line 19, return "%d" % int(d), will fail due to "OverflowError: long int too large to convert to int". Please describe a way to repeat the problem. Please try to provide a concise reproducible example, if at all possible: ---------------------------------------------------------------------- [1] create a table with a column type 'BIGINT'. [2] use pg.DB.insert() to insert a value that is larger than max integer If you know how this problem might be fixed, list the solution below: --------------------------------------------------------------------- Just changing the conversion at line 19 of pg.py to long(d) instead of int(d) should fix it. The following is a patch: Chih-Hao Huang
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 14:43:10 +0000