- 08 Jun, 2006 10 commits
-
-
Bruce Momjian authored
functions. I also found that pg_file_length was incorrectly documented in the README as pg_file_size.
-
Bruce Momjian authored
Robert Treat
-
Bruce Momjian authored
> * -Allow server logs to be remotely read and removed using SQL commands
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
> > See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php. >
-
Bruce Momjian authored
< recovery. > recovery. See http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php.
-
Bruce Momjian authored
< 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.
-
Bruce Momjian authored
< * Add SQL99 WITH RECURSIVE to SELECT > * Add SQL99 WITH RECURSIVE (hierarchical) queries to SELECT
-
Bruce Momjian authored
> * Consider allowing control of upper/lower case folding of unquoted > identifiers > > Details at http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php.
-
- 07 Jun, 2006 10 commits
-
-
Bruce Momjian authored
'2006-05-24 21:11 Americas/New_York'::timestamptz Joachim Wieland
-
Bruce Momjian authored
< o Allow timezone names in SQL strings, '2006-05-24 21:11 > o -Allow timezone names in SQL strings, '2006-05-24 21:11
-
Bruce Momjian authored
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
-
Bruce Momjian authored
Robert Treat
-
Bruce Momjian authored
> > Particularly, move GPL-licensed /contrib/userlock and > /contrib/dbmirror/clean_pending.pl. >
-
Tom Lane authored
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.
-
Bruce Momjian authored
-
Tom Lane authored
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.
-
Bruce Momjian authored
than only if there is already history.
-
Bruce Momjian authored
Euler Taveira de Oliveira
-
- 06 Jun, 2006 9 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
name, path does not exist), rather than returning nothing. Backpatch to 8.1.X.
-
Tom Lane authored
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.
-
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
-