summaryrefslogtreecommitdiff
path: root/doc/src
AgeCommit message (Collapse)Author
2006-03-01Update FAQ_DEV text file.Bruce Momjian
2006-03-01Update patch generation instructions.Bruce Momjian
Robert Treat
2006-03-01Update Japanese FAQ, backpatched to 8.1.X.Bruce Momjian
2006-03-01Add pg_service.conf documentation for libpq.Bruce Momjian
2006-02-25Fix computation of sample table size.Bruce Momjian
2006-02-24Backpatch FAQ changes to 8.1.X.Bruce Momjian
2006-02-24Mention that the archive history file has the wal start/stop file names.Bruce Momjian
2006-02-12Update release notes.Tom Lane
2006-02-12Fix broken markup.Tom Lane
2006-02-12Update wording for 8.1.X, remove <only>:Bruce Momjian
This option can <only> be set at server start or in the <filename>postgresql.conf</filename> configuration file.
2006-02-12> Actually, if you submit a patch that says either "SCROLL is theBruce Momjian
default" > or "NO SCROLL is the default", it will be rejected as incorrect. The > reason is that the default behavior is different from either of these, > as is explained in the NOTES section. Ok, so *that's* where the bit about the query plan being simple enough. Based on that, ISTM that it should be premissable for us to decide that a cursor requiring a sort isn't "simple enough" to support SCROLL. In any case, here's a patch that makes the non-standard behavior easier for people to find. Jim C. Nasby
2006-02-12Fix release item ordering.Bruce Momjian
2006-02-12Update back branch release notes.Bruce Momjian
2006-02-12Fix release markup.Bruce Momjian
2006-02-12Stamp 8.1.3, but exclude configure.in/configure change.Bruce Momjian
2006-02-12Update release notes for 8.1.3.Bruce Momjian
2006-02-09Reject out-of-range dates in date_in().Tom Lane
Kris Jurka
2006-02-05Fix typo in configuration docs.Bruce Momjian
Devrim GUNDUZ
2006-02-05Update PL/pgSQL trigger example to be clearer about how to "merge" dataBruce Momjian
into a table. Jim C. Nasby
2006-01-20Update EXPLAIN wording for GEQO usage.Bruce Momjian
2006-01-19Doc patch that adds an example of a correllated UPDATE.Bruce Momjian
David Fetter
2006-01-19Clarify STABLE function documentation to highlight how such functionsBruce Momjian
can be optimized.
2006-01-18Clarify use of btree indexes for ILIKE and ~*.Bruce Momjian
2006-01-12Remove extraneous backslash from 'fixseq.sql' example --- mea culpaTom Lane
certainly. Per report from George Woodring.
2006-01-06Release-note updates and copy editing.REL8_1_2Tom Lane
2006-01-05New pgcrypto item wording.Bruce Momjian
2006-01-05Wording improvements.Bruce Momjian
2006-01-05Improve markup.Bruce Momjian
2006-01-05Update release notes for 8.1.X, 8.0.X, 7.4.X, and 7.3.X.Bruce Momjian
2006-01-05Stamp release 8.1.2.Bruce Momjian
2005-12-29Remove a space that incorrectly precedes a comma in the PL/pgSQLBruce Momjian
documentation. Michael Fuhr
2005-12-28Update COPY CSV \. wording for externally created files.Bruce Momjian
2005-12-28Add regression tests for CSV and \., and add automatic quoting of aBruce Momjian
single column dump that has a \. value, so the load works properly. I also added documentation describing this issue. Backpatch to 8.1.X.
2005-12-22Update interval documenation to mention the storage system used.Bruce Momjian
2005-12-21Add documentation example of using interval multiplication with 'days'.Bruce Momjian
Backpatch to 8.1.X.
2005-12-21Add additional example for interval multiplication.Bruce Momjian
Fix example for day and hours interval subtraction for new computation method. Update interval examples to display zero seconds, which is our default. Backpatch to 8.1.X.
2005-12-09Add release notes for back branches (7.3 and up).Tom Lane
Also minor improvements to 8.1.1 release notes.
2005-12-09Add documentation about the behavior of BEFORE triggers and referentialBruce Momjian
integrity actions. Stephan Szabo
2005-12-09Remove mention that history is _now_ automatically saved on exit. ItBruce Momjian
has been that way for a long time.
2005-12-09Fix broken markup.Tom Lane
2005-12-08Release note wording improvements.Bruce Momjian
2005-12-08Wrap UTF-8 paragraph.Bruce Momjian
2005-12-08Update wording of translation bug item.Bruce Momjian
2005-12-08Stamp 8.1.1.Bruce Momjian
2005-12-08Update release notes for 8.1.1.Bruce Momjian
2005-12-08Update 8.1.X FAQs.Bruce Momjian
2005-12-08there's a paragraph in the ALTER TABLE reference page that reads:Bruce Momjian
DROP CONSTRAINT This form drops constraints on a table. Currently, constraints on tables are not required to have unique names, so there may be more than one constraint matching the specified name. All matching constraints will be dropped. To my knowledge, it is no longer possible to create constraints with the same name for the same relation. When you create a constraint and specify the same name explictly, an error is raised. Implicit constraint creation won't choose an existing name either and up to now you could not rename a constraint. Renaming works with the patch I sent in a few hours ago but this patch as well won't allow constraints with identical names on the same relation. The attached patch thus removes the note in the docs. Joachim Wieland
2005-12-08Remove empty heading row in error table.Bruce Momjian
2005-12-08Add "Constant" column to error code table.Bruce Momjian
Also, better mark section headings. kdio@uenf.br
2005-12-08Documentation fix: s/event_object_name/event_object_table/gPeter Eisentraut