- 06 Jun, 2006 6 commits
-
-
Bruce Momjian authored
< notify the protocol when a RESET CONNECTION command is used. > notify the protocol when a RESET CONNECTION command is used. See > http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php > for a partial implementation.
-
Teodor Sigaev authored
Docs will be submitted some later, now it's at http://www.sai.msu.su/~megera/oddmuse/index.cgi/Thesaurus_dictionary
-
Bruce Momjian authored
-
Bruce Momjian authored
Backpatch to 8.1.X.
-
Bruce Momjian authored
< * %Make postmater and postgres options distinct so the postmaster -o > * -Make postmater and postgres options distinct so the postmaster -o
-
Michael Meskes authored
Synced parser.
-
- 05 Jun, 2006 6 commits
-
-
Tom Lane authored
Per my proposal a few days ago.
-
Tom Lane authored
cost_nonsequential_access() is really totally inappropriate for its only remaining use, namely estimating I/O costs in cost_sort(). The routine was designed on the assumption that disk caching might eliminate the need for some re-reads on a random basis, but there's nothing very random in that sense about sort's access pattern --- it'll always be picking up the oldest outputs. If we had a good fix on the effective cache size we might consider charging zero for I/O unless the sort temp file size exceeds it, but that's probably putting much too much faith in the parameter. Instead just drop the logic in favor of a fixed compromise between seq_page_cost and random_page_cost per page of sort I/O.
-
Bruce Momjian authored
making it volatile.
-
Bruce Momjian authored
executed, like it did for 8.1.X.
-
Tom Lane authored
This shouldn't affect simple indexscans much, while for bitmap scans that are touching a lot of index rows, this seems to bring the estimates more in line with reality. Per recent discussion.
-
Tom Lane authored
assumed that a sequential page fetch has cost 1.0. This patch doesn't in itself change the system's behavior at all, but it opens the door to people adopting other units of measurement for EXPLAIN costs. Also, if we ever decide it's worth inventing per-tablespace access cost settings, this change provides a workable intellectual framework for that.
-
- 04 Jun, 2006 5 commits
-
-
Bruce Momjian authored
the query.
-
Bruce Momjian authored
< * %Remove behavior of postmaster -o > * %Make postmater and postgres options distinct so the postmaster -o > option is no longer needed
-
Bruce Momjian authored
< o Allow COPY to output from views > o Allow COPY to output from SELECT 570c570 < Another idea would be to allow actual SELECT statements in a COPY. > COPY should also be able to output views.
-
Bruce Momjian authored
Robert Treat
-
Bruce Momjian authored
Robert Treat
-
- 03 Jun, 2006 6 commits
-
-
Tom Lane authored
for LC_MESSAGES; instead, just press forward, leaving the effective setting at 'C'. There is not any very good reason to complain when we are going to replace the value soon with whatever postgresql.conf says. This change should solve the occasionally-reported problem of initdb failing with 'failed to initialize lc_messages'; the current theory is that that is a reflection of either wrong LANG/LC_MESSAGES or completely broken locale support.
-
Tom Lane authored
HAVE_INT64_TIMESTAMP was mentioning PG_CONTROL_VERSION instead. Victor Snezhko
-
Bruce Momjian authored
> * Allow WAL information to recover corrupted pg_controldata > > See partially completed patch and additional work required at > http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php. >
-
Tom Lane authored
Per Larry Rosenman.
-
Bruce Momjian authored
> * Allow WAL information to recover corrupted pg_controldata
-
- 02 Jun, 2006 3 commits
-
-
Teodor Sigaev authored
-
Teodor Sigaev authored
-
Teodor Sigaev authored
allow only recognized words in thezaurus configuration file.
-
- 01 Jun, 2006 3 commits
-
-
Tom Lane authored
see if using an intermediate variable avoids the gcc bug.
-
Tom Lane authored
E'...' syntax for strings in order to track the backend.
-
Tom Lane authored
and there's only one place that's a kluge, ie, appendStringLiteralConn. Note that pg_dump itself doesn't use appendStringLiteralConn, so its behavior is not affected; only the other utility programs care.
-
- 31 May, 2006 10 commits
-
-
Tom Lane authored
-
Tom Lane authored
NOT the thing to use here.
-
Tom Lane authored
the server. Per discussion, there seems no point in a waiting period before making this required.
-
Teodor Sigaev authored
-
Teodor Sigaev authored
It required some changes in lexize algorithm, but interface with dictionaries stays compatible with old dictionaries. Funded by Georgia Public Library Service and LibLime, Inc.
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
o turns off escape_string_warning in pg_dumpall.c o optionally use E'' for \password (undocumented option?) o honor standard_conforming-strings for \copy (but not support literal E'' strings) o optionally use E'' for \d commands o turn off escape_string_warning for createdb, createuser, droplang
-
Bruce Momjian authored
-
Michael Meskes authored
-
- 30 May, 2006 1 commit
-
-
Tom Lane authored
in every shared library.
-