aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* 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.
* Add URL to RESET CONNECTION:Bruce Momjian2006-06-06
| | | | | | | < 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.
* Allow do not lexize words in substitution.Teodor Sigaev2006-06-06
| | | | | Docs will be submitted some later, now it's at http://www.sai.msu.su/~megera/oddmuse/index.cgi/Thesaurus_dictionary
* Remove ancient AIX structure workaround.Bruce Momjian2006-06-06
|
* Have BCC echo output "" using "", rather than \"\" as earlier reported.Bruce Momjian2006-06-06
| | | | Backpatch to 8.1.X.
* Done:Bruce Momjian2006-06-06
| | | | | < * %Make postmater and postgres options distinct so the postmaster -o > * -Make postmater and postgres options distinct so the postmaster -o
* Fixed two more memory leaks in ecpglib.Michael Meskes2006-06-06
| | | | Synced parser.
* Remove extremely old, incomplete, broken example code.Tom Lane2006-06-05
| | | | Per my proposal a few days ago.
* While making the seq_page_cost changes, I was struck by the fact thatTom Lane2006-06-05
| | | | | | | | | | | | | 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.
* Avoid longjump/vfork warning about line_saved_in_history variable byBruce Momjian2006-06-05
| | | | making it volatile.
* Have psql history save \e editor contents to history before query isBruce Momjian2006-06-05
| | | | executed, like it did for 8.1.X.
* Increase the default value of cpu_index_tuple_cost from 0.001 to 0.005.Tom Lane2006-06-05
| | | | | | 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.
* Add a GUC parameter seq_page_cost, and use that everywhere we formerlyTom Lane2006-06-05
| | | | | | | | 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.
* Fix psql so \r is separate in the history, rather than at the end ofBruce Momjian2006-06-04
| | | | the query.
* Update:Bruce Momjian2006-06-04
| | | | | | < * %Remove behavior of postmaster -o > * %Make postmater and postgres options distinct so the postmaster -o > option is no longer needed
* Update:Bruce Momjian2006-06-04
| | | | | | | | < 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.
* Update GUI FAQ.Bruce Momjian2006-06-04
| | | | Robert Treat
* Update GUI tools URL.Bruce Momjian2006-06-04
| | | | Robert Treat
* Don't choke during startup if the environment offers an invalid valueTom Lane2006-06-03
| | | | | | | | | | 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.
* Fix copy-and-pasteo in Russian translation: message complaining aboutTom Lane2006-06-03
| | | | | HAVE_INT64_TIMESTAMP was mentioning PG_CONTROL_VERSION instead. Victor Snezhko
* Record location of partial patch :Bruce Momjian2006-06-03
| | | | | | | | > * 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. >
* Mention pg_encoding_to_char in entry for pg_database.encoding.Tom Lane2006-06-03
| | | | Per Larry Rosenman.
* Patch reverted, not done:Bruce Momjian2006-06-03
| | | | > * Allow WAL information to recover corrupted pg_controldata
* Remove pg_resetxlog -r flag, feature has problems referenced here:Bruce Momjian2006-06-03
| | | | http://archives.postgresql.org/pgsql-hackers/2006-05/msg00002.php
* Fix wrong NOTICE/ERROR levelsTeodor Sigaev2006-06-02
|
* Distinguish between stop-word recognized in thesaurus_lexize()Teodor Sigaev2006-06-02
|
* Add more strict check of stop and non-recognized words,Teodor Sigaev2006-06-02
| | | | allow only recognized words in thezaurus configuration file.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 00:02:56 +0000