aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* 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
* Remove:Bruce Momjian2006-06-09
| | | | < * Rename some /contrib modules from pg* to pg_*
* Fix bootstrap.c so that database startup process and bgwriter properly releaseTom Lane2006-06-08
| | | | | | | | | | | | LWLocks during a panic exit. This avoids the possible self-deadlock pointed out by Qingqing Zhou. Also, I noted that an error during LoadFreeSpaceMap() or BuildFlatFiles() would result in exit(0) which would leave the postmaster thinking all is well. Added a critical section to ensure such errors don't allow startup to proceed. Backpatched to 8.1. The 8.0 code is a bit different and I'm not sure if the problem exists there; given we've not seen this reported from the field, I'm going to be conservative about backpatching any further.
* Add URL.Bruce Momjian2006-06-08
| | | | | | > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php >
* Use simple URL's rather than text and a URL:Bruce Momjian2006-06-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | < recovery. See http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php. > recovery. > http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php < Right now only one encoding is allowed per database. For a partial < patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php. > Right now only one encoding is allowed per database. > http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php 459c460 < notify the protocol when a RESET CONNECTION command is used. See > notify the protocol when a RESET CONNECTION command is used. 461d461 < for a partial implementation. 515c515 < See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php. > http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php 535c535 < See http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php. > http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php 821c821 < See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php. > http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php 877c877 < Details at http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php. > http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php < See partially completed patch and additional work required at < http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php. > http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php 1297c1296 < See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php. > http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php 1311c1310,1311 < o Improve signal handling, > o Improve signal handling > 1312a1313 >
* Add URL.Bruce Momjian2006-06-08
| | | | | | | | < * Support triggers on columns (Greg Sabino Mullane) > * Support triggers on columns > > See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php. >
* Remove Win32 file, moved to /port.Bruce Momjian2006-06-08
| | | | Magnus Hagander
* Remove obsolete comment about VACUUM FULL: it takes buffer content locksTom Lane2006-06-08
| | | | | now, and must do so to ensure bgwriter doesn't write a page that is in process of being compacted.
* /contrib/adminpack: More clearly identify renaming of existing backendBruce Momjian2006-06-08
| | | | | functions. I also found that pg_file_length was incorrectly documented in the README as pg_file_size.
* Spelling fix.Bruce Momjian2006-06-08
| | | | Robert Treat
* Done:Bruce Momjian2006-06-08
| | | | > * -Allow server logs to be remotely read and removed using SQL commands
* Add missing 3rd argument to open().Bruce Momjian2006-06-08
|
* Add missing 3rd parameter to open().Bruce Momjian2006-06-08
|
* Add URL for ALTER CONSTRAINT RENAME.Bruce Momjian2006-06-08
| | | | | | > > See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php. >
* Add URL.Bruce Momjian2006-06-08
| | | | | < recovery. > recovery. See http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php.
* Add URL:Bruce Momjian2006-06-08
| | | | | | < Right now only one encoding is allowed per database. > Right now only one encoding is allowed per database. For a partial > patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php.
* Update wording:Bruce Momjian2006-06-08
| | | | | < * Add SQL99 WITH RECURSIVE to SELECT > * Add SQL99 WITH RECURSIVE (hierarchical) queries to SELECT
* Add entry:Bruce Momjian2006-06-08
| | | | | | | > * Consider allowing control of upper/lower case folding of unquoted > identifiers > > Details at http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php.
* Allow timezone names in SQL strings,Bruce Momjian2006-06-07
| | | | | | '2006-05-24 21:11 Americas/New_York'::timestamptz Joachim Wieland
* Done:Bruce Momjian2006-06-07
| | | | | < o Allow timezone names in SQL strings, '2006-05-24 21:11 > o -Allow timezone names in SQL strings, '2006-05-24 21:11
* Prepare code to be built by MSVC:Bruce Momjian2006-06-07
| | | | | | | | | | o remove many WIN32_CLIENT_ONLY defines o add WIN32_ONLY_COMPILER define o add 3rd argument to open() for portability o add include/port/win32_msvc directory for system includes Magnus Hagander
* Spelling fix.Bruce Momjian2006-06-07
| | | | Robert Treat
* Mention GPL /contrib modules:Bruce Momjian2006-06-07
| | | | | | | > > Particularly, move GPL-licensed /contrib/userlock and > /contrib/dbmirror/clean_pending.pl. >
* Per previous analysis, the most correct notion of SampleOverhead is thatTom Lane2006-06-07
| | | | | | | it is just the total time to do INSTR_TIME_SET_CURRENT(), and not any of the other code involved in InstrStartNode/InstrStopNode. Even though I fear we may end up reverting this patch altogether, we may as well have the most correct version in our CVS archive.
* Have REINDEX use NOTICE, so it can be suppressed.Bruce Momjian2006-06-07
|
* Remove "fuzzy comparison" logic in qsort comparison function forTom Lane2006-06-07
| | | | | | | | | | | | choose_bitmap_and(). It was way too fuzzy --- per comment, it was meant to be 1% relative difference, but was actually coded as 0.01 absolute difference, thus causing selectivities of say 0.001 and 0.000000000001 to be treated as equal. I believe this thinko explains Maxim Boguk's recent complaint. While we could change it to a relative test coded like compare_fuzzy_path_costs(), there's a bigger problem here, which is that any fuzziness at all renders the comparison function non-transitive, which could confuse qsort() to the point of delivering completely wrong results. So forget the whole thing and just do an exact comparison.
* For psql multi-line history, save backslash commands right away, ratherBruce Momjian2006-06-07
| | | | than only if there is already history.
* Use INFO-level for reindex messages, rather than NOTICE.Bruce Momjian2006-06-07
| | | | Euler Taveira de Oliveira
* Update comment.Bruce Momjian2006-06-06
|
* On Win32, return original patch if GetShortPathName() fails (no shortBruce Momjian2006-06-06
| | | | | | name, path does not exist), rather than returning nothing. Backpatch to 8.1.X.
* Make the planner estimate costs for nestloop inner indexscans on the basisTom Lane2006-06-06
| | | | | | | | | | | | | | | | | | | | | that the Mackert-Lohmann formula applies across all the repetitions of the nestloop, not just each scan independently. We use the M-L formula to estimate the number of pages fetched from the index as well as from the table; that isn't what it was designed for, but it seems reasonably applicable anyway. This makes large numbers of repetitions look much cheaper than before, which accords with many reports we've received of overestimation of the cost of a nestloop. Also, change the index access cost model to charge random_page_cost per index leaf page touched, while explicitly not counting anything for access to metapage or upper tree pages. This may all need tweaking after we get some field experience, but in simple tests it seems to be giving saner results than before. The main thing is to get the infrastructure in place to let cost_index() and amcostestimate functions take repeated scans into account at all. Per my recent proposal. Note: this patch changes pg_proc.h, but I did not force initdb because the changes are basically cosmetic --- the system does not look into pg_proc to decide how to call an index amcostestimate function, and there's no way to call such a function from SQL at all.
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-30 17:31:53 +0000