aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Add:Bruce Momjian2006-06-15
| | | | | | | > > o Fix memory leak from exceptions > > http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php
* Clarify dynamic pl/pgsql item and add URLs. Restructure server-sideBruce Momjian2006-06-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | section into PL/pgSQL and non-PL/pgSQL sections: < o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW < o Allow function parameters to be passed by name, < get_employee_salary(emp_id => 12345, tax_year => 2001) < o Add Oracle-style packages < o Add table function support to pltcl, plpython < o Add capability to create and call PROCEDURES < o Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[] < o Allow function argument names to be statements from PL/PgSQL < o Add MOVE to PL/pgSQL < o Add support for polymorphic arguments and return types to < languages other than PL/PgSQL < o Add support for OUT and INOUT parameters to languages other < than PL/PgSQL < o Add single-step debugging of PL/PgSQL functions < o Allow PL/PgSQL to support WITH HOLD cursors < o Allow PL/PgSQL RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php > o PL/pgSQL > o Fix RENAME to work on variables other than OLD/NEW > o Allow function parameters to be passed by name, > get_employee_salary(emp_id => 12345, tax_year => 2001) > o Add Oracle-style packages > o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[] > o Allow listing of record column names, and access to > record columns via variables, e.g. columns := r.(*), > tval2 := r.(colname) > > http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php > http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php > http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php > > o Add MOVE > o Add single-step debugging of functions > o Add support for WITH HOLD cursors > o Allow PL/RETURN to return row or record functions > > http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php > > > o Other > o Add table function support to pltcl, plpython > o Add support for polymorphic arguments and return types to > languages other than PL/PgSQL > o Add capability to create and call PROCEDURES > o Add support for OUT and INOUT parameters to languages other > than PL/PgSQL
* Add:Bruce Momjian2006-06-15
| | | | | | > o Allow PL/PgSQL RETURN to return row or record functions > > http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
* Done, removed:Bruce Momjian2006-06-15
| | | | | | | | < < * Consider padding the spinlock structure to have spinlock registers < on different CPU cache line < < http://archives.postgresql.org/pgsql-hackers/2005-10/msg00498.php
* Remove the limit on the number of entries allowed in catcaches, andTom Lane2006-06-15
| | | | | | | | | | | | | | | | | | remove the infrastructure needed to enforce the limit, ie, the global LRU list of cache entries. On small-to-middling databases this wins because maintaining the LRU list is a waste of time. On large databases this wins because it's better to keep more cache entries (we assume such users can afford to use some more per-backend memory than was contemplated in the Berkeley-era catcache design). This provides a noticeable improvement in the speed of psql \d on a 10000-table database, though it doesn't make it instantaneous. While at it, use per-catcache settings for the number of hash buckets per catcache, rather than the former one-size-fits-all value. It's a bit silly to be using the same number of hash buckets for, eg, pg_am and pg_attribute. The specific values I used might need some tuning, but they seem to be in the right ballpark based on CATCACHE_STATS results from the standard regression tests.
* Add to locale TODO.detail.Bruce Momjian2006-06-14
|
* Remove, done:Bruce Momjian2006-06-14
| | | | | | | < < * Add support for WIN1253 (Greek) encoding < < http://archives.postgresql.org/pgsql-bugs/2005-12/msg00000.php
* Add:Bruce Momjian2006-06-14
| | | | | | | > > * Add support for WIN1253 (Greek) encoding > > http://archives.postgresql.org/pgsql-bugs/2005-12/msg00000.php
* Add URL to ILIKE encoding fix:Bruce Momjian2006-06-14
| | | | > http://archives.postgresql.org/pgsql-patches/2005-11/msg00173.php
* Add:Bruce Momjian2006-06-14
| | | | | | | > > * Consider increasing internal areas when shared buffers is increased > > http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php
* Already done:Bruce Momjian2006-06-14
| | | | | | | < < o Properly mark all libpq-exported functions with "PQ" < < http://archives.postgresql.org/pgsql-hackers/2005-10/msg00696.php
* Done by Peter:Bruce Momjian2006-06-14
| | | | | | < * Improve the information schema to be more standards-compliant: < < http://archives.postgresql.org/pgsql-bugs/2005-10/msg00028.php
* Add:Bruce Momjian2006-06-14
| | | | | | | > > o Properly mark all libpq-exported functions with "PQ" > > http://archives.postgresql.org/pgsql-hackers/2005-10/msg00696.php
* Add:Bruce Momjian2006-06-14
| | | | | | | | > > * Consider padding the spinlock structure to have spinlock registers > on different CPU cache line > > http://archives.postgresql.org/pgsql-hackers/2005-10/msg00498.php
* Add item, not fixed:Bruce Momjian2006-06-14
| | | | | | | | > > * Fix ILIKE and regular expressions to handle case insensitivity > properly in multibyte encodings > > http://archives.postgresql.org/pgsql-bugs/2005-10/msg00001.php
* Remove, already in back branches:Bruce Momjian2006-06-14
| | | | | | | | | | | | | | < < o Add new version of PQescapeString() that doesn't double backslashes < that are part of a client-only multibyte sequence < < Single-quote is not a valid byte in any supported client-only < encoding. This requires using mblen() to determine if the < backslash is inside or outside a multi-byte sequence. < < o Add new version of PQescapeString() that doesn't double < backslashes when standard_conforming_strings is true and < non-E strings are used
* Done:Bruce Momjian2006-06-14
| | | | > o -Port contrib/xml2
* Add information schema item:Bruce Momjian2006-06-14
| | | | | | | | | | | | > * Improve the information schema to be more standards-compliant: > > http://archives.postgresql.org/pgsql-bugs/2005-10/msg00028.php > * Add URL to more complete multi-byte regression tests > > http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php < * Add URL to more complete multi-byte regression tests < < http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php
* Add COPY views patch URL:Bruce Momjian2006-06-14
| | | | > http://archives.postgresql.org/pgsql-patches/2005-09/msg00148.php
* Add:Bruce Momjian2006-06-14
| | | | | | | > > o Add API for 64-bit large object access > > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php
* Keep TODO.detail until item is done:Bruce Momjian2006-06-14
| | | | | < o %Allow pg_dump to use multiple -t and -n switches > o %Allow pg_dump to use multiple -t and -n switches [pg_dump]
* Add URL, remove TODO.detail:Bruce Momjian2006-06-14
| | | | | | | | < o %Allow pg_dump to use multiple -t and -n switches [pg_dump] > o %Allow pg_dump to use multiple -t and -n switches > > http://archives.postgresql.org/pgsql-patches/2006-01/msg00190.php >
* Add locale/encoding references:Bruce Momjian2006-06-14
| | | | | | < Right now only one encoding is allowed per database. > Right now only one encoding is allowed per database. [locale] > * Add CREATE COLLATE? [locale]
* Add locale TODO.detail emails.Bruce Momjian2006-06-14
|
* Update link to TODO.detail:Bruce Momjian2006-06-14
| | | | | < o Check WSACancelBlockingCall() for interrupts (win32intr) > o Check WSACancelBlockingCall() for interrupts [win32intr]
* Add:Bruce Momjian2006-06-14
| | | | | | | | > o Fix problem when cascading referential triggers make changes on > cascaded tables, seeing the tables in an intermediate state > > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
* Added:Bruce Momjian2006-06-14
| | | | | | | > > * Add URL to more complete multi-byte regression tests > > http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php
* Add entry:Bruce Momjian2006-06-14
| | | | | | > * Allow user-defined types to accept 'typmod' parameters > http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php
* Further thoughts about lo_export/lo_import error handling: if one ofTom Lane2006-06-14
| | | | | | | the lower-level large object functions fails, it will have already set a suitable error message --- probably something from the backend --- and it is not useful to overwrite that with a generic 'error while reading large object' message. So remove redundant messages.
* Clean up psql's control-C handling to avoid longjmp'ing out of randomTom Lane2006-06-14
| | | | | | | | | places --- that risks corrupting data structures, losing sync with the backend, etc. We now longjmp only from calls to readline, fgets, and fread, which we assume are coded to protect themselves against interrupts at undesirable times. This requires adding explicit tests for cancel_pressed in long-running loops, but on the whole it's far cleaner. Martijn van Oosterhout and Tom Lane.
* Improve error detection and recovery in lo_import()/lo_export().Tom Lane2006-06-14
| | | | Problems noted while experimenting with new control-C code for psql.
* Do a CHECK_FOR_INTERRUPTS immediately before terminating a fastpathTom Lane2006-06-14
| | | | | | | | | function call. Previously, there may have been no CHECK_FOR_INTERRUPTS at all in the fastpath code path, making it impossible to cancel an operation such as \lo_import externally. This addition doesn't ensure you can cancel, since your SIGINT may arrive while the backend is idle waiting for the client, but it gives the largest window we can easily provide. Noted while experimenting with new control-C code for psql.
* Remove:Bruce Momjian2006-06-13
| | | | < o %Add CSV output format
* Add BY clause to PL/PgSQL FOR loop, to control the iteration increment.Bruce Momjian2006-06-12
| | | | Jaime Casanova
* Avoid use of C commment inside C comment from recent Win32 int overflow patch.Bruce Momjian2006-06-12
|
* Prevent Win32 from displaying a popup box on backend crash. Instead letBruce Momjian2006-06-12
| | | | | | the postmaster deal with it. Magnus Hagander
* Add URL for bitmap AM:Bruce Momjian2006-06-12
| | | | > http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php
* Win32 can't catch the exception thrown by INT_MIN / -1 or INT_MIN * -1,Bruce Momjian2006-06-12
| | | | | | | so on that platform we test for those before the computation and throw an "out of range" error. Backpatch to 8.1.X.
* Minor code cleanup: make the WIN32 case less gratuitously different fromTom Lane2006-06-12
| | | | the other platform-specific cases in ps_status.
* Code review for psql multiline history patch(es). Fix memory leak,Tom Lane2006-06-11
| | | | | failure to enter commands in history if canceled by control-C, other infelicities.
* Fix Assert failure when a fastpath function call is attempted inside anTom Lane2006-06-11
| | | | | | | | | | | | | | | already-aborted transaction block. GetSnapshotData throws an Assert if not in a valid transaction; hence we mustn't attempt to set a snapshot for the function until after checking for aborted transaction. This is harmless AFAICT if Asserts aren't enabled (GetSnapshotData will compute a bogus snapshot, but it doesn't matter since HandleFunctionRequest will throw an error shortly anywy). Hence, not a major bug. Along the way, add some ability to log fastpath calls when statement logging is turned on. This could probably stand to be improved further, but not logging anything is clearly undesirable. Backpatched as far as 8.0; bug doesn't exist before that.
* Remove pg_dump wording:Bruce Momjian2006-06-10
| | | | | | < pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef(), and < make use of them in pg_dump > pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef()
* Add:Bruce Momjian2006-06-10
| | | | | | < pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef() > pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef(), and > make use of them in pg_dump
* Repair remarkably-inefficient query for dumping large object comments: itTom Lane2006-06-09
| | | | | | was invoking obj_description() for each large object chunk, instead of once per large object. This code is new as of 8.1, which may explain why the problem hadn't been noticed already.
* Revert sampling patch for EXPLAIN ANALYZE; it turns out to be too unreliableTom Lane2006-06-09
| | | | | because node timing is much less predictable than the patch expects. I kept the API change for InstrStopNode, however.
* Cleanups:Bruce Momjian2006-06-09
| | | | | | | | | | | | | | < * Allow a database in tablespace t1 with tables created in > o Allow a database in tablespace t1 with tables created in 125c125 < * Allow reporting of which objects are in which tablespaces > o Allow reporting of which objects are in which tablespaces 593c593 < * Allow GRANT/REVOKE permissions to be inherited by objects based on > o Allow GRANT/REVOKE permissions to be inherited by objects based on 596c596 < * Allow SERIAL sequences to inherit permissions from the base table? > o Allow SERIAL sequences to inherit permissions from the base table?
* Cleanup:Bruce Momjian2006-06-09
| | | | | < * -%Allow pooled connections to list all prepared statements > * -Allow pooled connections to list all prepared statements
* Now ispell dictionary can eat dictionaries in MySpell format,Teodor Sigaev2006-06-09
| | | | | | | | | | | | | used by OpenOffice. Dictionaries are placed at http://lingucomponent.openoffice.org/spell_dic.html Dictionary automatically recognizes format of files. Warning. MySpell's format has limitation with compound word support: it's impossible to mark affix as compound-only affix. So for norwegian, german etc languages it's recommended to use original ispell format. For that reason I don't want to remove my2ispell scripts, it's has workaround at least for norwegian language.
* Add URL.Bruce Momjian2006-06-09
| | | | | | < the insert. > the insert. > http://archives.postgresql.org/pgsql-patches/2005-07/msg00568.php
* Update:Bruce Momjian2006-06-09
| | | | | < * Add SQL99 WITH RECURSIVE (hierarchical) queries to SELECT > * Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 14:46:49 +0000