aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Doug Fields patch to prevent exception being thrown on zero length arraysDave Cramer2002-03-05
|
* patch from Zhenbang WeiDave Cramer2002-03-05
| | | | | The errors_zh_TW.properties must be translated using native2ascii or it will raise an exception. Please replace the old file.
* Patch from Ryouichi MatsudaDave Cramer2002-03-05
| | | | | | | | | | | | | | | | An attached patch corrects problem of this bug and fractional second. The handling of time zone was as follows: (a) with time zone using SimpleDateFormat("yyyy-MM-dd HH:mm:ss z") (b) without time zone using SimpleDateFormat("yyyy-MM-dd HH:mm:ss") About problem of fractional second, Fractional second was changed from milli-second to nano-second
* patch from Mitchel Friedman to fix getTablesDave Cramer2002-03-05
|
* Showing index details with \d on psql.Bruce Momjian2002-03-05
| | | | Greg Sabino Mullane
* patch from Vicktor to fix Numeric decimal digits in getColumnsDave Cramer2002-03-05
|
* Back out python patch:Bruce Momjian2002-03-05
| | | | | | | | Elliot Lee wrote: > This patch to the python bindings adds C versions of the often-used query > args quoting routines, as well as support for quoting lists e.g. > dbc.execute("SELECT * FROM foo WHERE blah IN %s", ([1,2,3],))
* This patch to the python bindings adds C versions of the often-usedBruce Momjian2002-03-05
| | | | | | | query args quoting routines, as well as support for quoting lists e.g. dbc.execute("SELECT * FROM foo WHERE blah IN %s", ([1,2,3],)) Elliot Lee
* Add \timing patch to psql. Times all queries.Bruce Momjian2002-03-05
| | | | Greg Sabino Mullane
* Add PQunescapeBytea libpq function.Bruce Momjian2002-03-04
| | | | | | Everyone using libpq and bytea is probably having to invent this wheel.. Patrick Welche
* Improve libpgeasy API for multiple result sets, add example.Bruce Momjian2002-03-04
|
* Add Assert check to catch vsnprintf overrunning its buffer. (Seen toTom Lane2002-03-04
| | | | occur on Solaris 7 in 64-bit mode, for one.)
* Make port makefile slightly less crufty.Tom Lane2002-03-04
|
* Fix very ancient breakage in alter-table tests: apparently, there was aTom Lane2002-03-04
| | | | | | type named 'dt' back in Postgres 4.2, and the regression test wasn't updated when it was removed. Per report from Patricia Holben of Great Bridge.
* If presented db path has a trailing slash, remove it to avoid generatingTom Lane2002-03-04
| | | | | double slashes in generated filenames. This is not strictly necessary on standard Unixen, but I'm being a neatnik...
* Fix bug in extract/date_part for milliseconds/miscroseconds andTatsuo Ishii2002-03-04
| | | | | | | | | | | timestamp/timestamptz combo. Now extract/date_part returns seconds*1000 or 1000000 + fraction part as the manual stats. regression test are also fixed. See the thread in pgsql-hackers: Subject: Re: [HACKERS] timestamp_part() bug? Date: Sat, 02 Mar 2002 11:29:53 +0900
* Fix bogus error check in pg_execute, per report from lbayuk@mindspring.com.Tom Lane2002-03-04
|
* Further work on elog cleanup: fix some bogosities in elog's logic aboutTom Lane2002-03-04
| | | | | | | when to send what to which, prevent recursion by introducing new COMMERROR elog level for client-communication problems, get rid of direct writes to stderr in backend/libpq files, prevent non-error elogs from going to client during the authentication cycle.
* Catcaches can now store negative entries as well as positive ones, toTom Lane2002-03-03
| | | | | | | | | | speed up repetitive failed searches; per pghackers discussion in late January. inval.c logic substantially simplified, since we can now treat inserts and deletes alike as far as inval events are concerned. Some repair work needed in heap_create_with_catalog, which turns out to have been doing CommandCounterIncrement at a point where the new relation has non-self-consistent catalog entries. With the new inval code, that resulted in assert failures during a relcache entry rebuild.
* Default server_min_messages is NOTICE.Bruce Momjian2002-03-03
|
* Cause regression tests to pass again after elog changes.Tom Lane2002-03-03
|
* Some kibitzing about appropriate elog levels for sinval messages.Tom Lane2002-03-02
|
* Commit to match discussed elog() changes. Only update is that LOG isBruce Momjian2002-03-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | now just below FATAL in server_min_messages. Added more text to highlight ordering difference between it and client_min_messages. --------------------------------------------------------------------------- REALLYFATAL => PANIC STOP => PANIC New INFO level the prints to client by default New LOG level the prints to server log by default Cause VACUUM information to print only to the client NOTICE => INFO where purely information messages are sent DEBUG => LOG for purely server status messages DEBUG removed, kept as backward compatible DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1 added DebugLvl removed in favor of new DEBUG[1-5] symbols New server_min_messages GUC parameter with values: DEBUG[5-1], INFO, NOTICE, ERROR, LOG, FATAL, PANIC New client_min_messages GUC parameter with values: DEBUG[5-1], LOG, INFO, NOTICE, ERROR, FATAL, PANIC Server startup now logged with LOG instead of DEBUG Remove debug_level GUC parameter elog() numbers now start at 10 Add test to print error message if older elog() values are passed to elog() Bootstrap mode now has a -d that requires an argument, like postmaster
* Add code to allow profiling of backends on Linux: save and restore theTom Lane2002-03-02
| | | | | profiling timer setting across fork(). The correct way to build a profilable backend on Linux is now gmake PROFILE="-pg -DLINUX_PROFILE"
* Don't bother to request SSL connection over a Unix socket, since theTom Lane2002-03-02
| | | | | postmaster won't accept the request anyway. (If your kernel can't be trusted, SSL will not help you.)
* Array slice extraction should produce a result array with index lowerTom Lane2002-03-02
| | | | | bounds of 1, not the lower bound subscripts of the original slice. Per bug report from Andre Holzner, 1-Feb-02.
* User and database-specific session defaults for run-time configurationPeter Eisentraut2002-03-01
| | | | variables. New commands ALTER DATABASE ... SET and ALTER USER ... SET.
* array_ref() should set isNull to false explicitly if it's not going toPeter Eisentraut2002-03-01
| | | | return NULL.
* Fix thinko: cost_mergejoin must pay attention to which side of theTom Lane2002-03-01
| | | | mergeclause is which when extracting selectivity info.
* Add files for Unicode support.Hiroshi Inoue2002-03-01
|
* Second thoughts dept: arrange to cache mergejoin scan selectivityTom Lane2002-03-01
| | | | in RestrictInfo nodes, instead of recomputing on every use.
* Teach planner about the idea that a mergejoin won't necessarily readTom Lane2002-03-01
| | | | | | both input streams to the end. If one variable's range is much less than the other, an indexscan-based merge can win by not scanning all of the other table. Per example from Reinhard Max.
* Tweak pg_exec_query_string so that we close down transaction commandTom Lane2002-02-27
| | | | | | | | | before reporting command-complete message for the final command of a query string. This way, any errors detected during finish_xact_command (such as RI violations) will appear to be part of the final command, rather than coming out after the command is reported complete. This avoids confusing PQendcopy and other not-overly-bright clients. Per Lee Harr's bug report of 25-Feb-02.
* #ifdef out pg_dump's check on whether a sequence's sequence_name fieldTom Lane2002-02-27
| | | | | | matches the sequence name from pg_class. This fails if the sequence has been renamed, and seems rather pointless in any case. Also improve a couple of error messages about inconsistencies.
* Paranoia about data structure lifetime ...Tom Lane2002-02-27
|
* Clean up BeginCommand and related routines. BeginCommand and EndCommandTom Lane2002-02-27
| | | | | | | | | | | are now both invoked once per received SQL command (raw parsetree) from pg_exec_query_string. BeginCommand is actually just an empty routine at the moment --- all its former operations have been pushed into tuple receiver setup routines in printtup.c. This makes for a clean distinction between BeginCommand/EndCommand (once per command) and the tuple receiver setup/teardown routines (once per ExecutorRun call), whereas the old code was quite ad hoc. Along the way, clean up the calling conventions for ExecutorRun a little bit.
* Improve the handling of ODBC escape(a request from Marcelo Aceto).Hiroshi Inoue2002-02-27
| | | | | Change SQLGetFunctions() to reply not yet implemented ODBC 3.0 functions precisely.
* Fix bug in COPY FROM when DELIMITER is not in ASCII range.Tatsuo Ishii2002-02-27
| | | | | See pgsql-bugs/pgsql-hackers discussion "COPY FROM is not 8bit clean" around 2002/02/26 for more details -- Tatsuo Ishii
* Restructure command-completion-report code so that there is just oneTom Lane2002-02-26
| | | | | | | report for each received SQL command, regardless of rewriting activity. Also ensure that this report comes from the 'original' command, not the last command generated by rewrite; this fixes 7.2 breakage for INSERT commands that have actions added by rules. Fernando Nasser and Tom Lane.
* Implementation for cancelQuery by Grant Finnemore <grantf@guruhut.co.za>Dave Cramer2002-02-26
|
* Use quote-marks to try to clarify a plpgsql error message, perTom Lane2002-02-26
| | | | gripe from Dan Langille.
* Tweak psql's \connect command to not downcase unquoted database and userTom Lane2002-02-25
| | | | | | | | names. This is a temporary measure to allow backwards compatibility with 7.2 and earlier pg_dump. 7.2.1 and later pg_dump will double-quote mixed case names in \connect. Once we feel that older dumps are not a problem anymore, we can revert this change and treat \connect arguments as normal SQL identifiers.
* Fix for PAM error message display:Bruce Momjian2002-02-25
| | | | | | | > and that the right fix is to make each of the subsequent calls be in > this same pattern, not to try to emulate their nonsensical style. Dominic J. Eidson
* Add note that BLCKSZ must be a power of 2.Tom Lane2002-02-25
|
* Add a large number of time zones to the lookup table.Thomas G. Lockhart2002-02-25
| | | | Fix a few apparently-wrong TZ vs DTZ declarations.
* This patch will allow arbitrary levels of analyze / rewritingBruce Momjian2002-02-25
| | | | | | | | | | | | | | | | | | by making the static variables extra_before and extra_after automatic so we can use recursion. It gets much easier to generate extra commands now, and one can rest assured that the extra commands will be properly analyzed/rewritten. Without this patch, if a command produced by transformation tries to use these static lists their first contents would be lost with unpredictable results. I know I could fix this by just using nconc() instead of assignments, but the resulting order of the commands would not be exactly what one could expect. -- Fernando Nasser
* I've attached a simple patch which should improve the performance ofBruce Momjian2002-02-25
| | | | | | | | | | | | | | hashname() and reduce the penalty incured when NAMEDATALEN is increased. I posted this to -hackers a couple days ago, and there haven't been any major complaints. It passes the regression tests. See -hackers for more discussion, as well as the suggestion from Tom Lane on which this patch is based. Unless anyone sees any problems, please apply for 7.3. Cheers, Neil Conway
* Re-add equals documentation with CREATE DATABASE.Bruce Momjian2002-02-25
|
* Remove documentation of equals in CREATE DATABASE. Mention removal ofBruce Momjian2002-02-25
| | | | equals hack for the future.
* Fix bogus createdb option syntax recommended by initlocation message.Tom Lane2002-02-24
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 18:23:25 +0000