- 08 6月, 2006 4 次提交
-
-
由 Bruce Momjian 提交于
> > Particularly, move GPL-licensed /contrib/userlock and > /contrib/dbmirror/clean_pending.pl. >
-
由 Tom Lane 提交于
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 提交于
-
由 Tom Lane 提交于
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.
-
- 07 6月, 2006 9 次提交
-
-
由 Bruce Momjian 提交于
than only if there is already history.
-
由 Bruce Momjian 提交于
Euler Taveira de Oliveira
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
name, path does not exist), rather than returning nothing. Backpatch to 8.1.X.
-
由 Tom Lane 提交于
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 提交于
< 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 提交于
Docs will be submitted some later, now it's at http://www.sai.msu.su/~megera/oddmuse/index.cgi/Thesaurus_dictionary
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Backpatch to 8.1.X.
-
- 06 6月, 2006 4 次提交
-
-
由 Bruce Momjian 提交于
< * %Make postmater and postgres options distinct so the postmaster -o > * -Make postmater and postgres options distinct so the postmaster -o
-
由 Michael Meskes 提交于
Synced parser.
-
由 Tom Lane 提交于
Per my proposal a few days ago.
-
由 Tom Lane 提交于
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.
-
- 05 6月, 2006 4 次提交
-
-
由 Bruce Momjian 提交于
making it volatile.
-
由 Bruce Momjian 提交于
executed, like it did for 8.1.X.
-
由 Tom Lane 提交于
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 提交于
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 6月, 2006 7 次提交
-
-
由 Bruce Momjian 提交于
the query.
-
由 Bruce Momjian 提交于
< * %Remove behavior of postmaster -o > * %Make postmater and postgres options distinct so the postmaster -o > option is no longer needed
-
由 Bruce Momjian 提交于
< 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 提交于
Robert Treat
-
由 Bruce Momjian 提交于
Robert Treat
-
由 Tom Lane 提交于
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 提交于
HAVE_INT64_TIMESTAMP was mentioning PG_CONTROL_VERSION instead. Victor Snezhko
-
- 03 6月, 2006 6 次提交
-
-
由 Bruce Momjian 提交于
> * 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 提交于
Per Larry Rosenman.
-
由 Bruce Momjian 提交于
> * Allow WAL information to recover corrupted pg_controldata
-
由 Teodor Sigaev 提交于
-
由 Teodor Sigaev 提交于
-
- 02 6月, 2006 1 次提交
-
-
由 Teodor Sigaev 提交于
allow only recognized words in thezaurus configuration file.
-
- 01 6月, 2006 5 次提交
-
-
由 Tom Lane 提交于
see if using an intermediate variable avoids the gcc bug.
-
由 Tom Lane 提交于
E'...' syntax for strings in order to track the backend.
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
NOT the thing to use here.
-