rdelaage/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-09-30 21:21:16 +02:00
Code Issues Packages Projects Releases Wiki Activity
24,228 Commits 36 Branches 606 Tags 423 MiB
9e9e387ecf
Commit Graph

7417 Commits

Author SHA1 Message Date
Tom Lane
aec4cf1c8c Add a function pg_stat_clear_snapshot() that discards any statistics snapshot 
already collected in the current transaction; this allows plpgsql functions to
watch for stats updates even though they are confined to a single transaction.
Use this instead of the previous kluge involving pg_stat_file() to wait for
the stats collector to update in the stats regression test.  Internally,
decouple storage of stats snapshots from transaction boundaries; they'll
now stick around until someone calls pgstat_clear_snapshot --- which xact.c
still does at transaction end, to maintain the previous behavior.  This makes
the logic a lot cleaner, at the price of a couple dozen cycles per transaction
exit.
 2007-02-07 23:11:30 +00:00
Bruce Momjian
a3f9a054c1 Stamp bug template for 8.3. 2007-02-07 05:14:08 +00:00
Bruce Momjian
cf230f2299 Stamp releases notes for 8.2.3, 8.1.8, 8.0.12. 2007-02-07 04:22:44 +00:00
Bruce Momjian
ced5269a8b Update for 8.2.3. 2007-02-07 03:16:22 +00:00
Bruce Momjian
09f9553daf Update for 8.2.2 as most recent release. 2007-02-06 18:36:26 +00:00
Bruce Momjian
63b7afbe4f Update workding for daylight savings time. 2007-02-06 18:33:20 +00:00
Bruce Momjian
a85a290dad Update timezone FAQ item: 
<P>USA saving time changes are included in PostgreSQL release 8.0.[4+],
    and all later major releases, e.g. 8.1.  Canada and Western Australia
    changes are included in 8.0.[10+], 8.1.[6+], and all later major
    releases.  PostgreSQL releases prior to 8.0 use the operating system's
    timezone database for daylight saving information.</P>
 2007-02-06 18:31:26 +00:00
Bruce Momjian
869585cc8f Split apart entries, one done now: 
* -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h
* Consider making NAMEDATALEN more configurable in future releases
 2007-02-06 16:44:14 +00:00
Peter Eisentraut
037f8413fa Move NAMEDATALEN definition from postgres_ext.h to pg_config_manual.h. It 
used to be part of libpq's exported interface many releases ago, but now
it's no longer necessary to make it accessible to clients.
 2007-02-06 09:16:08 +00:00
Tom Lane
91e18dbbcc Docs updates for cross-type hashing. 2007-02-06 04:38:31 +00:00
Tom Lane
b259924e9f Not only did we agree that this 'hint' doesn't belong here, but the 
markup's broken.  So just remove it...
 2007-02-06 03:03:11 +00:00
Bruce Momjian
b70e536e4d Trim down environment variable instructions for Win32, backpatch to 8.2.X. 2007-02-05 22:18:11 +00:00
Bruce Momjian
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
Bruce Momjian
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
Bruce Momjian
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
Bruce Momjian
1a476a6145 Update wording. 2007-02-04 04:00:28 +00:00
Bruce Momjian
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
Bruce Momjian
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
Bruce Momjian
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
Bruce Momjian
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
Bruce Momjian
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
Bruce Momjian
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
Peter Eisentraut
4c488e857e Update SQL conformance information about XML features. 2007-02-03 17:59:36 +00:00
Bruce Momjian
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
Bruce Momjian
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
Bruce Momjian
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
Bruce Momjian
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
Neil Conway
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
Bruce Momjian
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
Tom Lane
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
Tom Lane
dc4c26c37e Fix broken markup. 2007-02-01 22:06:14 +00:00
Bruce Momjian
f7e5ecb026 Add "May/Can/Might" section to error message style guidlines, and 
"can't" -> "cannot" section.
 2007-02-01 21:28:34 +00:00
Bruce Momjian
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
Tom Lane
a9d5fb5a02 Typo fix. 2007-02-01 20:28:08 +00:00
Bruce Momjian
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
Bruce Momjian
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
Neil Conway
baaec74c5a Fix broken markup. 2007-02-01 07:00:32 +00:00
Bruce Momjian
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
Bruce Momjian
969320c8b8 Chinese FAQ update 
Daojing.Zhou
 2007-02-01 04:55:53 +00:00
Bruce Momjian
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
Bruce Momjian
2ccb40b532 Add: 
>
> * Tighten function permission checks
>
>   http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php
>
 2007-02-01 04:50:58 +00:00
Bruce Momjian
fa3f06dc6b Add: 
>
> * Tighten trigger permission checks
>
>   http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php
>
 2007-02-01 04:49:43 +00:00
Neil Conway
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
Bruce Momjian
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
Bruce Momjian
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
Bruce Momjian
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
Bruce Momjian
09a9f10e7f Consistenly use colons before '<programlisting>' blocks, where 
appropriate.
 2007-02-01 00:28:19 +00:00
Bruce Momjian
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
Bruce Momjian
482e6936fa Revert error message change for may/can/might --- needs discussion. 2007-01-31 21:03:37 +00:00
Bruce Momjian
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