aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Add option to output SET SESSION AUTHORIZATION commands rather thanPeter Eisentraut2001-08-22
| | | | | \connect, to avoid possible password prompts and such, at the drawback of having to have superuser access.
* remove no longer needed -Wno-errorPeter Eisentraut2001-08-22
|
* Update GiST for new pg_opclass arrangement (finally a clean solutionTom Lane2001-08-22
| | | | | | for haskeytype). Update GiST contrib modules too. Add linear-time split algorithm for R-tree GiST opclass. From Oleg Bartunov and Teodor Sigaev.
* Attached is a simple one line patch for the problem reported in theBruce Momjian2001-08-22
| | | | | | | | | | | | | | | following email. > > The problem: When I call getBigDecimal() on a ResultSet, it > > sometimes throws an exception: > > > > Bad BigDecimal 174.50 > > at org.postgresql.jdbc2.ResultSet.getBigDecimal(ResultSet.java:373) > > at org.postgresql.jdbc2.ResultSet.getBigDecimal(ResultSet.java:984) > > ...blah blah blah... > > org.postgresql.util.PSQLException: Bad BigDecimal 174.50 Barry Lind
* Here's a resend of the patch.gz. I gunzip'ed it fine hereBruce Momjian2001-08-21
| | | | | | | | | | | | so it may be a transit problem. Also removed the 'txt' suffix in case that was confusing some transport layer trying to be too inteligent for our own good. This may have been because the Array.java class from the previous patch didn't seem to have made it into the snapshot build for some reason. This patch should at least fix that issue. Greg Zoller
* Remove special-case treatment of all-zeroes MAC address, per today'sTom Lane2001-08-21
| | | | discussion in pgsql-general.
* > Ok, where's a "system dependent hack" :)Bruce Momjian2001-08-21
| | | | | | | | | | | | | | | | | | | | > It seems that win9x doesn't have the "netmsg.dll" so it defaults to "normal" > FormatMessage. > I wonder if one could load wsock32.dll or winsock.dll on those systems > instead of netmsg.dll. > > Mikhail, could you please test this code on your nt4 system? > Could someone else test this code on a win98/95 system? > > It works on win2k over here. It works on win2k here too but not on win98/95 or winNT. Anyway, attached is the patch which uses Magnus's my_sock_strerror function (renamed to winsock_strerror). The only difference is that I put the code to load and unload netmsg.dll in the libpqdll.c (is this OK Magnus?). Mikhail Terekhov
* Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions inTom Lane2001-08-21
| | | | | | | | | | | | | | | | | | | | pgsql-hackers. pg_opclass now has a row for each opclass supported by each index AM, not a row for each opclass name. This allows pg_opclass to show directly whether an AM supports an opclass, and furthermore makes it possible to store additional information about an opclass that might be AM-dependent. pg_opclass and pg_amop now store "lossy" and "haskeytype" information that we previously expected the user to remember to provide in CREATE INDEX commands. Lossiness is no longer an index-level property, but is associated with the use of a particular operator in a particular index opclass. Along the way, IndexSupportInitialize now uses the syscaches to retrieve pg_amop and pg_amproc entries. I find this reduces backend launch time by about ten percent, at the cost of a couple more special cases in catcache.c's IndexScanOK. Initial work by Oleg Bartunov and Teodor Sigaev, further hacking by Tom Lane. initdb forced.
* Move WAL params higher in file, next to fsync option.Bruce Momjian2001-08-21
|
* Add -Wno-error because of "unclean" flex output.Peter Eisentraut2001-08-21
|
* Regroup GEQO configs.Bruce Momjian2001-08-21
|
* Fix SCM_CREDS for FreeBSD, from Teodor Sigaev.Bruce Momjian2001-08-21
|
* Add new jdbc array file.Bruce Momjian2001-08-21
|
* Add ECPGd_cardinality to end of enum list so ecpg compiles.Bruce Momjian2001-08-21
|
* Add missing include for SCM_CREDS.Bruce Momjian2001-08-21
|
* Fix SO_PEERCRED printf bug added with SCM_CREDS cleanup.Bruce Momjian2001-08-21
|
* Fix a lot of compile errors on unix.Hiroshi Inoue2001-08-21
| | | | Fix '\\' handling for bytea type.
* >Bruce Momjian2001-08-21
| | | | | | | | | | | | | | | | | | | | > Shouldn't > > throw new PSQLException("metadata unavailable"); > > in getTypeInfo() be something like: > > throw new PSQLException("postgresql.meta.unavailable"); > > to allow translation of the error message in the > errors*.properties files? You're right. Attached is an updated patch that also includes a message in error.properties. I've attempted a French message in errors_fr.properties but beware that I haven't written French in quite a few years. Don't know Italian, German, or Dutch so I can't do those. Liam Stewart
* Add SCM_CREDS to get owner of unix-domain socket on BSD-like systems.Bruce Momjian2001-08-21
|
* One more round of translations and slight message tweaksPeter Eisentraut2001-08-19
|
* - Synced preproc.y with gram.y.Michael Meskes2001-08-19
| | | | - Include some patches by Christof Petig <christof.petig@wtal.de>.
* 1) Change all internal SQL function calls fromHiroshi Inoue2001-08-18
| | | | | | | | SQLxxxx() to PGAPI_xxxx(). 2) Handle an escaped date/time format as a parameter. 3) Improve the tuple allocation a little. 4) The preparation of ODBC 3.0 a little. 5) Updatable cursors(may be deprecated before long).
* Ensure to hold an exclusive lock while reindexing a relation.Hiroshi Inoue2001-08-17
| | | | This is mainly to help developers to understand the code.
* A little more code reorg for MD5/crypt.Bruce Momjian2001-08-17
|
* Reorder MD5/crypt so MD5 comes first in the code.Bruce Momjian2001-08-17
|
* Remove some unneeded dashes from libpq comments.Bruce Momjian2001-08-17
|
* Add \n to libpq print output where needed.Bruce Momjian2001-08-17
|
* This patch updates some comments in the DatabaseMetaData classes toBruce Momjian2001-08-17
| | | | | | | reflect a mail thread that discussed our conformance (or lack thereof) to the SQL92 spec. Barry Lind
* Thanks for your feedback (and patience). Enclosed is my thirdBruce Momjian2001-08-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | attempt at a patch to 7.1.2 to support Array. [I think I've solved the mangled patch problem. Hotmail seems to try to format the text file, so gzipping it should solve this problem.] In this patch I've incorporated Barry's feedback. Specifically: 1) OIDs are no longer hard-coded into Array.java. In order to support this change I added a getOID(String) method to Field.java which receives a PostgreSQL field type and returns a value from java.sql.Types. I couldn't get away from using OIDs altogether because the JDBC spec for Array specifies that some methods return a ResultSet. This requires I construct Field objects, which means I need OIDs. At least this approach doesn't hard code these values. A Hashtable cache has been added to Field so that an SQL lookup isn't necessary (following the model already in Field.java). 2) Rewired the base formatting code in ResultSet.java to use 'to' methods, which are then exposed as static methods in ResultSet. These methods are used in Array to format the data without duplications in the code. 3) Artifact call to first() in ResultSet.getArray() removed. Greg Zoller
* Attached is the patch requested by Tom Lane (see below). ItBruce Momjian2001-08-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | includes two changes in the JDBC driver: 1) When connected to a backend >= 7.2: use obj_description() and col_description() instead of direct access to pg_description. 2) In DatabaseMetaData.getTables()/getColumns()/getProcedures(): when there is no comment on the object, return null in the REMARKS column of the ResultSet, instead of the default string "no remarks". Change 2 first appeared as a side-effect of change 1, but it is actually more compliant with the JDBC spec: "String object containing an explanatory comment on the table/column/procedure, which may be null". The default string "no remarks" was strictly speaking incorrect, as it could not be distinguished from a real user comment "no remarks". So I removed the default string completely. Change 2 might break existing code that doesn't follow the JDBC spec and isn't prepared to handle a null in the REMARKS column of getTables()/getColumns()/getProcedures. Patch tested with jdbc2 against both a 7.1 and a CVS tip backend. I did not have a jdbc1 environment to build and test with, but since the touched code is identical in jdbc1 and jdbc2 I don't foresee any problems. Regards, Ren? Pijlman
* Force crypt() salt to be null-terminated.Bruce Momjian2001-08-17
|
* Add 4-byte MD5 salt.Bruce Momjian2001-08-17
|
* Update list of files to update.Bruce Momjian2001-08-16
|
* Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-typeTom Lane2001-08-16
| | | | | | | | has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
* Add new MD5 pg_hba.conf keyword. Prevent fallback to crypt.Bruce Momjian2001-08-16
|
* This patch fixes the well-known but unfixed bug that fetchone() always returnsBruce Momjian2001-08-16
| | | | | | | the first result in the DB-API compliant wrapper. It turned out that the bug was way down in the C code. Gerhard Häring
* Remove protocol version change. Try MD5 first, then crypt() on all clients.Bruce Momjian2001-08-16
|
* Use malloc/palloc as appropriate.Bruce Momjian2001-08-15
|
* Move md5.h contents to crypt.h.Bruce Momjian2001-08-15
|
* Add new files.Bruce Momjian2001-08-15
|
* Use MD5 for wire protocol encryption for >= 7.2 client/server.Bruce Momjian2001-08-15
| | | | | | | Allow pg_shadow to be MD5 encrypted. Add ENCRYPTED/UNENCRYPTED option to CREATE/ALTER user. Add password_encryption postgresql.conf option. Update wire protocol version to 2.1.
* Add conver/convert2 functions. They are similar to the SQL99's convert.Tatsuo Ishii2001-08-15
|
* sum() on int2 and int4 columns now uses an int8, not numeric, accumulatorTom Lane2001-08-14
| | | | | | | | | | | | | | | | | | | | for speed reasons; its result type also changes to int8. avg() on these datatypes now accumulates the running sum in int8 for speed; but we still deliver the final result as numeric, so that fractional accuracy is preserved. count() now counts and returns in int8, not int4. I am a little nervous about this possibly breaking users' code, but there didn't seem to be a strong sentiment for avoiding the problem. If we get complaints during beta, we can change count back to int4 and add a "count8" aggregate. For that matter, users can do it for themselves with a simple CREATE AGGREGATE command; the int4inc function is still present, so no C hacking is needed. Also added max() and min() aggregates for OID that do proper unsigned comparison, instead of piggybacking on int4 aggregates. initdb forced.
* Fix brokenness of nested EXCEPT/INTERSECT queries. prepunion was beingTom Lane2001-08-14
| | | | | | a tad sloppy about generating the targetlist for some nodes, by generating a tlist entry that claimed to be a constant when the value wasn't actually constant. This caused setrefs.c to do the wrong thing later on.
* Make LANCOMPILER clause in CREATE LANGUAGE optional. Allow "identifier"Peter Eisentraut2001-08-13
| | | | | | | | | | | | syntax for language names (instead of 'string'). createlang now handles the case where a second language uses the same call handler as an already installed language (e.g., plperl/plperlu). droplang now handles the reverse case, i.e., dropping a language where the call handler is still used by another language. Moreover, droplang can now be used to drop any user-defined language, not just the supplied ones.
* Make hashjoin give the right answer with toasted input data.Tom Lane2001-08-13
|
* Add comparison operators and btree indexing support for type bytea.Tom Lane2001-08-13
| | | | From Joe Conway.
* Make ALTER TABLE RENAME on a view rename the view's on-select rule too.Tom Lane2001-08-12
| | | | Needed to keep pg_dump from getting confused.
* Make pg_dump handle the new privileges.Peter Eisentraut2001-08-12
| | | | | | Don't hardcode the maximum accepted server version, use PG_VERSION instead. Install a notice processor so notices are handled like error messages. Word smithing.
* Clean up some warnings and bugs and make things build easier.Peter Eisentraut2001-08-11
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-02 05:11:26 +0000