aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
* Update FAQ_DEV text file.Bruce Momjian2006-03-01
|
* Update patch generation instructions.Bruce Momjian2006-03-01
| | | | Robert Treat
* Update Japanese FAQ, backpatched to 8.1.X.Bruce Momjian2006-03-01
|
* Add pg_service.conf documentation for libpq.Bruce Momjian2006-03-01
|
* Fix computation of sample table size.Bruce Momjian2006-02-25
|
* Backpatch FAQ changes to 8.1.X.Bruce Momjian2006-02-24
|
* Mention that the archive history file has the wal start/stop file names.Bruce Momjian2006-02-24
|
* Update release notes.Tom Lane2006-02-12
|
* Fix broken markup.Tom Lane2006-02-12
|
* Update wording for 8.1.X, remove <only>:Bruce Momjian2006-02-12
| | | | | This option can <only> be set at server start or in the <filename>postgresql.conf</filename> configuration file.
* > Actually, if you submit a patch that says either "SCROLL is theBruce Momjian2006-02-12
| | | | | | | | | | | | | | | | 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
* Fix release item ordering.Bruce Momjian2006-02-12
|
* Update back branch release notes.Bruce Momjian2006-02-12
|
* Fix release markup.Bruce Momjian2006-02-12
|
* Stamp 8.1.3, but exclude configure.in/configure change.Bruce Momjian2006-02-12
|
* Update release notes for 8.1.3.Bruce Momjian2006-02-12
|
* Reject out-of-range dates in date_in().Tom Lane2006-02-09
| | | | Kris Jurka
* Fix typo in configuration docs.Bruce Momjian2006-02-05
| | | | Devrim GUNDUZ
* Update PL/pgSQL trigger example to be clearer about how to "merge" dataBruce Momjian2006-02-05
| | | | | | into a table. Jim C. Nasby
* Update EXPLAIN wording for GEQO usage.Bruce Momjian2006-01-20
|
* Doc patch that adds an example of a correllated UPDATE.Bruce Momjian2006-01-19
| | | | David Fetter
* Clarify STABLE function documentation to highlight how such functionsBruce Momjian2006-01-19
| | | | can be optimized.
* Clarify use of btree indexes for ILIKE and ~*.Bruce Momjian2006-01-18
|
* Remove extraneous backslash from 'fixseq.sql' example --- mea culpaTom Lane2006-01-12
| | | | certainly. Per report from George Woodring.
* Release-note updates and copy editing.REL8_1_2Tom Lane2006-01-06
|
* New pgcrypto item wording.Bruce Momjian2006-01-05
|
* Wording improvements.Bruce Momjian2006-01-05
|
* Improve markup.Bruce Momjian2006-01-05
|
* Update release notes for 8.1.X, 8.0.X, 7.4.X, and 7.3.X.Bruce Momjian2006-01-05
|
* Stamp release 8.1.2.Bruce Momjian2006-01-05
|
* Remove a space that incorrectly precedes a comma in the PL/pgSQLBruce Momjian2005-12-29
| | | | | | documentation. Michael Fuhr
* Update COPY CSV \. wording for externally created files.Bruce Momjian2005-12-28
|
* Add regression tests for CSV and \., and add automatic quoting of aBruce Momjian2005-12-28
| | | | | | | single column dump that has a \. value, so the load works properly. I also added documentation describing this issue. Backpatch to 8.1.X.
* Update interval documenation to mention the storage system used.Bruce Momjian2005-12-22
|
* Add documentation example of using interval multiplication with 'days'.Bruce Momjian2005-12-21
| | | | Backpatch to 8.1.X.
* Add additional example for interval multiplication.Bruce Momjian2005-12-21
| | | | | | | | | 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.
* Add release notes for back branches (7.3 and up).Tom Lane2005-12-09
| | | | Also minor improvements to 8.1.1 release notes.
* Add documentation about the behavior of BEFORE triggers and referentialBruce Momjian2005-12-09
| | | | | | integrity actions. Stephan Szabo
* Remove mention that history is _now_ automatically saved on exit. ItBruce Momjian2005-12-09
| | | | has been that way for a long time.
* Fix broken markup.Tom Lane2005-12-09
|
* Release note wording improvements.Bruce Momjian2005-12-08
|
* Wrap UTF-8 paragraph.Bruce Momjian2005-12-08
|
* Update wording of translation bug item.Bruce Momjian2005-12-08
|
* Stamp 8.1.1.Bruce Momjian2005-12-08
|
* Update release notes for 8.1.1.Bruce Momjian2005-12-08
|
* Update 8.1.X FAQs.Bruce Momjian2005-12-08
|
* there's a paragraph in the ALTER TABLE reference page that reads:Bruce Momjian2005-12-08
| | | | | | | | | | | | | | | | | | | | | 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
* Remove empty heading row in error table.Bruce Momjian2005-12-08
|
* Add "Constant" column to error code table.Bruce Momjian2005-12-08
| | | | | | Also, better mark section headings. kdio@uenf.br
* Documentation fix: s/event_object_name/event_object_table/gPeter Eisentraut2005-12-08
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-17 20:15:13 +0000