sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-13 01:13:08 -04:00
Code Issues Projects Releases Wiki Activity
21,656 Commits 37 Branches 654 Tags
Commit Graph

6316 Commits

Author SHA1 Message Date
Bruce Momjian
15516c5f0b Update FAQ_DEV text file. 2006-03-01 22:25:36 +00:00
Bruce Momjian
88a4314bb1 Update patch generation instructions. 
Robert Treat
 2006-03-01 22:23:49 +00:00
Bruce Momjian
e559dba846 Update Japanese FAQ, backpatched to 8.1.X. 2006-03-01 20:31:56 +00:00
Bruce Momjian
6853e34132 Add pg_service.conf documentation for libpq. 2006-03-01 00:23:33 +00:00
Bruce Momjian
3952eecd4a Fix computation of sample table size. 2006-02-25 04:30:06 +00:00
Bruce Momjian
032858216c Backpatch FAQ changes to 8.1.X. 2006-02-24 15:00:48 +00:00
Bruce Momjian
39825338b4 Mention that the archive history file has the wal start/stop file names. 2006-02-24 14:03:11 +00:00
Tom Lane
ef434ebfbc Update release notes. 2006-02-12 22:35:36 +00:00
Tom Lane
b71e2bb122 Fix broken markup. 2006-02-12 21:13:00 +00:00
Bruce Momjian
544ccf6ce6 Update wording for 8.1.X, remove <only>: 
This option can <only> be set at server start or in the
        <filename>postgresql.conf</filename> configuration file.
 2006-02-12 19:19:37 +00:00
Bruce Momjian
a22873a19e > Actually, if you submit a patch that says either "SCROLL is the 
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-12 19:02:28 +00:00
Bruce Momjian
34d9bbee4d Stamp releases for 2006-02-14 release 2006-02-12 18:42:20 +00:00
Bruce Momjian
003daafb0d Fix release item ordering. 2006-02-12 18:14:29 +00:00
Bruce Momjian
12ea69aaf5 Update back branch release notes. 2006-02-12 17:58:31 +00:00
Bruce Momjian
d9dafcc5d6 Fix release markup. 2006-02-12 17:28:23 +00:00
Bruce Momjian
a318438fb3 Stamp 8.1.3, but exclude configure.in/configure change. 2006-02-12 17:17:39 +00:00
Bruce Momjian
3a9c81e3e9 Update release notes for 8.1.3. 2006-02-12 17:11:28 +00:00
Tom Lane
f527f082c5 Reject out-of-range dates in date_in(). 
Kris Jurka
 2006-02-09 03:40:30 +00:00
Bruce Momjian
c75c372c58 Fix typo in configuration docs. 
Devrim GUNDUZ
 2006-02-05 18:19:33 +00:00
Bruce Momjian
3bf6284f10 Update PL/pgSQL trigger example to be clearer about how to "merge" data 
into a table.

Jim C. Nasby
 2006-02-05 02:48:20 +00:00
Bruce Momjian
4a651c9705 Update EXPLAIN wording for GEQO usage. 2006-01-20 16:42:02 +00:00
Bruce Momjian
936433ba53 Doc patch that adds an example of a correllated UPDATE. 
David Fetter
 2006-01-19 23:09:46 +00:00
Bruce Momjian
b148ce8a4a Clarify STABLE function documentation to highlight how such functions 
can be optimized.
 2006-01-19 22:52:20 +00:00
Bruce Momjian
2e2c4f424f Clarify use of btree indexes for ILIKE and ~*. 2006-01-18 22:26:01 +00:00
Tom Lane
34b0ac6ada Remove extraneous backslash from 'fixseq.sql' example --- mea culpa 
certainly.  Per report from George Woodring.
 2006-01-12 18:09:42 +00:00
Tom Lane
68f4ed462a Release-note updates and copy editing. 2006-01-06 03:00:06 +00:00
Bruce Momjian
ffc7186004 New pgcrypto item wording. 2006-01-05 15:19:52 +00:00
Bruce Momjian
61180e80d4 Wording improvements. 2006-01-05 15:13:26 +00:00
Bruce Momjian
045de2d865 Improve markup. 2006-01-05 14:54:07 +00:00
Bruce Momjian
e0f1f8ad0b Update release notes for 8.1.X, 8.0.X, 7.4.X, and 7.3.X. 2006-01-05 05:16:03 +00:00
Bruce Momjian
f54a68d24a Stamp release 8.1.2. 2006-01-05 04:02:26 +00:00
Bruce Momjian
8136eca59c Remove a space that incorrectly precedes a comma in the PL/pgSQL 
documentation.

Michael Fuhr
 2005-12-29 04:02:41 +00:00
Bruce Momjian
c54fee814f Update COPY CSV \. wording for externally created files. 2005-12-28 14:38:43 +00:00
Bruce Momjian
c7fc2ccf63 Add regression tests for CSV and \., and add automatic quoting of a 
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-28 05:38:27 +00:00
Bruce Momjian
f545a05704 Update interval documenation to mention the storage system used. 2005-12-22 21:45:30 +00:00
Bruce Momjian
14e9a17f0a Add documentation example of using interval multiplication with 'days'. 
Backpatch to 8.1.X.
 2005-12-21 23:23:09 +00:00
Bruce Momjian
2469b99665 Add additional example for interval multiplication. 
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-21 16:02:44 +00:00
Tom Lane
a2fc8ca797 Add release notes for back branches (7.3 and up). 
Also minor improvements to 8.1.1 release notes.
 2005-12-09 20:40:26 +00:00
Bruce Momjian
24cea65634 Add documentation about the behavior of BEFORE triggers and referential 
integrity actions.

Stephan Szabo
 2005-12-09 19:39:43 +00:00
Bruce Momjian
2eed0afc0c Remove mention that history is _now_ automatically saved on exit. It 
has been that way for a long time.
 2005-12-09 19:19:28 +00:00
Tom Lane
9af49fcf87 Fix broken markup. 2005-12-09 18:07:57 +00:00
Bruce Momjian
df56447077 Release note wording improvements. 2005-12-08 23:22:38 +00:00
Bruce Momjian
d4fa3a8c78 Wrap UTF-8 paragraph. 2005-12-08 22:45:51 +00:00
Bruce Momjian
9f389f7db9 Update wording of translation bug item. 2005-12-08 22:36:52 +00:00
Bruce Momjian
96a1732710 Stamp 8.1.1. 2005-12-08 22:31:10 +00:00
Bruce Momjian
4bafc1202a Update release notes for 8.1.1. 2005-12-08 22:22:27 +00:00
Bruce Momjian
5e6e9526c9 Update 8.1.X FAQs. 2005-12-08 21:37:54 +00:00
Bruce Momjian
e2d7e03fb2 FAQ_AIX in 8.1.0 contains outdated information about how to deal with 
postgres problems due to readline.  The attached patch replaces that
section of it with better ways of handling the problem.

Seneca Cunningham
 2005-12-08 21:36:55 +00:00
Bruce Momjian
6c8e20ad1b there's a paragraph in the ALTER TABLE reference page that reads: 
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-08 21:35:41 +00:00
Bruce Momjian
8c52b34bc7 Remove empty heading row in error table. 2005-12-08 21:23:13 +00:00