fdd4a1ff0d
Updated TODO item:
...
> o Add a \set variable to control whether \s displays line numbers
> Another option is to add \# which lists line numbers, and
> allows command execution.
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
2007-02-05 17:17:13 +00:00
fcbddea8b7
Modify:
...
< o Add \# to list command history like \s, but with line numbers
> o Add \# to list and execute command history
2007-02-05 16:49:13 +00:00
03d442ca60
Add:
...
>
> * Allow custom variable classes that can restrict who can set the values
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php
>
2007-02-04 04:06:08 +00:00
1a476a6145
Update wording.
2007-02-04 04:00:28 +00:00
43aa1e59f5
Add documentation for Windows on how to set an environment variable.
...
Backpatch to 8.2.X.
2007-02-04 03:55:51 +00:00
1d6653ee80
Update URL for:
...
* Allow sequential scans to take advantage of other concurrent
sequential scans, also called "Synchronised Scanning"
2007-02-04 02:32:03 +00:00
28019984e9
Add:
...
>
> o Add \# to list command history like \s, but with line numbers
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
>
2007-02-04 01:50:59 +00:00
300c43e303
Add URLs for:
...
* Allow sequential scans to take advantage of other concurrent
sequential scans, also called "Synchronised Scanning"
> http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php
2007-02-03 23:52:19 +00:00
1a641c0cee
Document that a client-only install using:
...
gmake -C src/bin install
does install a few server-only binaries.
2007-02-03 23:01:06 +00:00
b6f6284802
Add:
...
> o Allow recovery.conf to allow the same syntax as
> postgresql.conf, including quoting
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php
2007-02-03 22:32:49 +00:00
4c488e857e
Update SQL conformance information about XML features.
2007-02-03 17:59:36 +00:00
b1b9c364cc
Add patches thread for:
...
* Reduce checkpoint performance degredation by forcing data to disk
more evenly
> http://archives.postgresql.org/pgsql-patches/2006-12/msg00104.php
2007-02-03 01:59:27 +00:00
635425d845
Add URL for:
...
* Allow sequential scans to take advantage of other concurrent
sequential scans, also called "Synchronised Scanning"
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php
2007-02-02 23:05:36 +00:00
69b90c49bc
Add:
...
> * Reduce checkpoint performance degredation by forcing data to disk
> more evenly
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00337.php
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg00079.php
2007-02-02 22:55:08 +00:00
99be3fa3ee
Add URL for:
...
o Fix RENAME to work on variables other than OLD/NEW
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php
2007-02-02 21:34:39 +00:00
ee84009cb0
Reword suggestion that libpq.dll be installed in WINNT\SYSTEM32 under
...
Windows. Per Magnus Hagander, this is not recommended.
2007-02-02 16:10:08 +00:00
98df90013f
Add:
...
> o Allow column display reordering by recording a display,
> storage, and permanent id for every column?
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php
>
2007-02-02 05:42:56 +00:00
bd01a4e3b7
Update release notes for security-related releases in all active branches.
...
Security: CVE-2007-0555, CVE-2007-0556
2007-02-02 00:10:23 +00:00
dc4c26c37e
Fix broken markup.
2007-02-01 22:06:14 +00:00
f7e5ecb026
Add "May/Can/Might" section to error message style guidlines, and
...
"can't" -> "cannot" section.
2007-02-01 21:28:34 +00:00
52096ae119
Mention file system replication as a high availability solution in the
...
shared hardware section, and mention DRBD as a popular solution.
2007-02-01 21:02:48 +00:00
a9d5fb5a02
Typo fix.
2007-02-01 20:28:08 +00:00
db047e571d
Add URL for:
...
o Add long file support for binary pg_dump output
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00551.php
2007-02-01 19:13:56 +00:00
8b4ff8b6a1
Wording cleanup for error messages. Also change can't -> cannot.
...
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 19:10:30 +00:00
baaec74c5a
Fix broken markup.
2007-02-01 07:00:32 +00:00
f1b68860bc
Add 8.2.0 "Incomatibilities" documentation that pg_dump's -n and -t
...
behavior has changed.
2007-02-01 05:12:24 +00:00
969320c8b8
Chinese FAQ update
...
Daojing.Zhou
2007-02-01 04:55:53 +00:00
a867c5aa2f
Update URL for function permission checks
...
< http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00568.php
>
2007-02-01 04:51:31 +00:00
2ccb40b532
Add:
...
>
> * Tighten function permission checks
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php
>
2007-02-01 04:50:58 +00:00
fa3f06dc6b
Add:
...
>
> * Tighten trigger permission checks
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php
>
2007-02-01 04:49:43 +00:00
bd2c171414
This patch adds documentation for the long-version parameters --username
...
and --password for pg_dump, pg_dumpall and pg_restore, per complaint by
Michael Schmidt. Patch from Magnus Hagander.
2007-02-01 04:39:33 +00:00
e665137250
Add:
...
>
> * Fix problem when multiple subtransactions of the same outer transaction
> hold different types of locks, and one subtransaction aborts
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php
2007-02-01 04:35:52 +00:00
b3687889c4
Update CREATE SEQUENCE documentation to show the same sequence being
...
created and increments. The old docs created the sequence, then showed
a nextval() of 114.
2007-02-01 00:34:03 +00:00
40bf8717cf
Add URL for:
...
o Fix RENAME to work on variables other than OLD/NEW
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg01615.php
2007-02-01 00:32:45 +00:00
09a9f10e7f
Consistenly use colons before '<programlisting>' blocks, where
...
appropriate.
2007-02-01 00:28:19 +00:00
e81c138e18
Update reference documentation on may/can/might:
...
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-01-31 23:26:05 +00:00
482e6936fa
Revert error message change for may/can/might --- needs discussion.
2007-01-31 21:03:37 +00:00
a134ee3379
Update documentation on may/can/might:
...
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
Also update two error messages mentioned in the documenation to match.
2007-01-31 20:56:20 +00:00
b62f85691e
Update FreeBSD DocBook installation notices
2007-01-31 15:23:28 +00:00
d4c6da1527
Allow GIN's extractQuery method to signal that nothing can satisfy the query.
...
In this case extractQuery should returns -1 as nentries. This changes
prototype of extractQuery method to use int32* instead of uint32* for
nentries argument.
Based on that gincostestimate may see two corner cases: nothing will be found
or seqscan should be used.
Per proposal at http://archives.postgresql.org/pgsql-hackers/2007-01/msg01581.php
PS tsearch_core patch should be sightly modified to support changes, but I'm
waiting a verdict about reviewing of tsearch_core patch.
2007-01-31 15:09:45 +00:00
147a3ce149
Add URL:
...
o Fix RENAME to work on variables other than OLD/NEW
>
> http://archives.postgresql.org/pgsql-hackers/2002-03/msg00591.php
>
2007-01-31 04:23:47 +00:00
0867493510
Document need for periodic REINDEX in VACUUM FULL cases.
2007-01-31 04:13:22 +00:00
1a62813464
Add missing colon.
2007-01-31 04:12:01 +00:00
99507b9a92
Add:
...
>
> * Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
>
> This is difficult because you must upgrade to an exclusive table lock
> to replace the existing index file. CREATE INDEX CONCURRENTLY does not
> have this complication. This would allow index compaction without
> downtime.
2007-01-31 03:17:49 +00:00
62b2786b82
Update for VACUUM FULL:
...
< reindex rather than update the index.
> reindex rather than update the index. Also, index updates can
> bloat the index.
2007-01-31 03:07:36 +00:00
aca00a8b98
Add:
...
> o ARRAY[[1,2],[3,4]])[1] should return the same values as
> ARRAY[[1,2],[3,4]])[1:1];
>
2007-01-30 22:55:12 +00:00
91a753f68b
Add FAQ item about timezones and daylight savings time.
2007-01-30 22:37:15 +00:00
4ed9f1d9b7
Update documentation for backslashes to mention escape string syntax
...
more, and standard_conforming_strings less, because in the future non-E
strings will not treat backslashes specially.
Also use E'' strings where backslashes are used in examples. (The
existing examples would have drawn warnings.)
Backpatch to 8.2.X.
2007-01-30 22:29:23 +00:00
ae875d318e
Update documentation for pg_get_serial_sequence() function.
2007-01-30 02:39:27 +00:00
c120dd263b
Update wording for minor release upgrades, per Alvaro.
2007-01-29 21:49:17 +00:00
Bruce Momjian
Peter Eisentraut
Neil Conway
Tom Lane
Teodor Sigaev