1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-09 22:41:56 +03:00
Commit Graph

9383 Commits

Author SHA1 Message Date
09bcb24806 Minor wordsmithing in release notes' description of asynchronous commit. 2008-02-02 23:30:23 +00:00
19c40492f0 Move example of turning off synchronous_commit to a more logical place,
to wit in the description of that variable rather than some other one.
2008-02-02 23:29:12 +00:00
1ac09940db Update FAQ for most recent release as 8.3. 2008-02-01 02:55:41 +00:00
ea3db8f79d Update item:
< * Improve deadlock detection when deleting items from shared buffers
> * Improve deadlock detection when a page cleaning lock conflicts
>   with a shared buffer that is pinned
2008-02-01 02:41:10 +00:00
b07e548590 Fix spelling typo in comment. 2008-01-31 23:31:33 +00:00
694403d30e Add comment about possible URL changes for www7.hp.com:
<!-- If this URL chnages replace it with a URL to www.archive.org. -->
2008-01-31 23:30:31 +00:00
162dc31428 Update spoofing /tmp symlink instructions to be more specific about the
name of the needed symlink file.
2008-01-31 23:03:16 +00:00
06462f51e3 Mention synchronize_seqscans GUC variable in release notes.
Update expected release date.
2008-01-31 21:31:33 +00:00
73d9544e27 Remove the old table of "supported platforms" in favor of a link to the
buildfarm plus a narrative description of the CPU types and operating systems
on which Postgres is likely to work.  Now that we've almost completely
decoupled CPU and OS considerations, the former tabular style isn't all that
enlightening anyway.  Perhaps more importantly, no one seems particularly
interested in maintaining the table by hand when we have the buildfarm.
2008-01-31 20:29:30 +00:00
7c15b10a9a Improve pg_autovacuum documentation to clarify that the enabled field cannot
prevent anti-wraparound vacuuming, and to caution against setting unreasonably
small values of freeze_max_age.  Also put in a notice that this catalog is
likely to disappear entirely in some future release.  Per discussion of
bug #3898 from Steven Flatt.
2008-01-31 18:40:02 +00:00
8e9c7fe982 Document the idea of creating a symbolic link in /tmp to prevent server
spoofing when the socket file has been moved.
2008-01-31 17:22:43 +00:00
55986a5eb8 Add:
> * Improve deadlock detection when deleting items from shared buffers
>
>   http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php
>   http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php
>   http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php
2008-01-31 15:05:09 +00:00
47df4f6688 Add a GUC variable "synchronize_seqscans" to allow clients to disable the new
synchronized-scanning behavior, and make pg_dump disable sync scans so that
it will reliably preserve row ordering.  Per recent discussions.
2008-01-30 18:35:55 +00:00
f73f18f92c Improve table reference 2008-01-30 10:49:55 +00:00
c7640c3298 Update key words table for 8.3 2008-01-30 10:37:36 +00:00
65b39ec347 Update wording:
< * Add anonymous transactions
> * Add autonomous transactions
2008-01-29 16:13:09 +00:00
1567133511 Add item:
> * Add anonymous transactions
>
>   http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php
>
2008-01-29 16:11:19 +00:00
522f362975 Remove duplicat item:
< 	  o Allow the PITR process to be debugged and data examined
2008-01-29 16:09:28 +00:00
a38fae6c75 markup correct
from Gevik Babakhani
2008-01-29 13:03:50 +00:00
cf9990c66e Add "Communication Method" row to HA feature matrix documentation. 2008-01-28 18:43:55 +00:00
b5518c8e88 Minor editorial improvements in documentation of session_replication_role;
in particular correct the obsolete claim that it can't be changed once
any plans have been cached.
2008-01-27 19:12:28 +00:00
a794b99a31 Fix example of de-escaping bytea argument, per Florian Weimer. Also fix example
of escaping bytea return value. Both cases did not handle backslash values properly.
2008-01-25 15:28:35 +00:00
79a323ab49 Change /contrib to contrib for consistency. 2008-01-24 06:23:33 +00:00
1570d0467a Provide a concrete example of parameter expansion in archive_command.
Per discussion of bug #3877.  Simon Riggs, some fixes by moi.
2008-01-23 20:21:37 +00:00
216e63bbce Avoid mathematical inconsistency in example about avoiding division by
zero with a CASE expression.  Per gripe from Russell Smith.
2008-01-23 19:51:29 +00:00
6a7a63d3a3 Reference pgAdmin as a typical client-side tool, rather than the
no-longer-maintained PgAccess.  Per Erik Rijkers.
2008-01-23 02:04:47 +00:00
1e985720eb Improve description of bgwriter_lru_multiplier, per discussion. 2008-01-21 03:28:42 +00:00
7b4be2ba2f Stamp release for 8.3RC2; configure will be stamped by packager. 2008-01-18 00:13:50 +00:00
d07de6c4ec Update Japanese FAQ.
Jun Kuwamura
2008-01-17 18:53:20 +00:00
e467168e32 Typo fix.
Erik Rijkers
2008-01-17 14:34:45 +00:00
98bb697f33 pgcrypto doc updates
Marko Kreen
2008-01-17 11:06:28 +00:00
c7d7c15bb1 Document the fact that COPY always uses the client encoding. 2008-01-16 22:07:04 +00:00
0153c4c466 Be less wishy-washy in the documentation and comments about whether a
ParameterStatus message can be sent during COPY OUT: it's definitely
possible, since COPY from a SELECT subquery can trigger any user-defined
function.
2008-01-15 22:18:20 +00:00
abab776b3c Somebody forgot to add this ERRCODE everywhere it should go ... 2008-01-15 01:36:53 +00:00
1272ac82b6 Add:
>
> * Add the ability to automatically create materialized views
>
>   Right now materialized views require the user to create triggers on the
>   main table to keep the summary table current.  SQL syntax should be able
>   to manager the triggers and summary table automatically.  A more
>   sophisticated implementation would automatically retrieve from the
>   summary table when the main table is referenced, if possible.
>
2008-01-14 22:14:30 +00:00
be8451e548 Most recent Postgres version is 8.2.6, per report from Robert Treat. 2008-01-14 20:39:30 +00:00
5c7671425f Fix an ancient oversight in libpq's handling of V3-protocol COPY OUT mode:
we need to be able to swallow NOTICE messages, and potentially also
ParameterStatus messages (although the latter would be a bit weird),
without exiting COPY OUT state.  Fix it, and adjust the protocol documentation
to emphasize the need for this.  Per off-list report from Alexander Galler.
2008-01-14 18:46:17 +00:00
05a381add9 Add note pointing out that read-only commands no longer consume
command IDs.
2008-01-13 17:58:54 +00:00
9f2a20b66d Update documentation for tsvector duplicate elimination:
!      Duplicate positions for the same lexeme are discarded.
2008-01-12 21:51:36 +00:00
f3e3f2e158 Add:
> * Add ability to trigger on TRUNCATE
>
>   http://archives.postgresql.org/pgsql-sql/2008-01/msg00050.php
2008-01-11 16:49:27 +00:00
ccd3e321f7 Add index entry. 2008-01-09 05:27:22 +00:00
3048964e65 Remove mention of /contrib README files from documentation because files
are moved to SGML.
2008-01-09 02:37:45 +00:00
bbd3bdba3e Add URLs to two excellent web pages about SSL API and certificate usage. 2008-01-08 18:07:38 +00:00
99749f3306 Put spaces after "RFC". 2008-01-05 13:17:00 +00:00
88a79c1d61 Add URL for:
* Allow AS in "SELECT col AS label" to be optional (not wanted)

>   http://archives.postgresql.org/pgsql-hackers/2003-04/msg00436.php
2008-01-04 15:58:27 +00:00
019fac777d Update release notes for security releases.
Security: CVE-2007-4769, CVE-2007-4772, CVE-2007-6067, CVE-2007-6600, CVE-2007-6601
2008-01-03 21:35:25 +00:00
eedb068c0a Make standard maintenance operations (including VACUUM, ANALYZE, REINDEX,
and CLUSTER) execute as the table owner rather than the calling user, using
the same privilege-switching mechanism already used for SECURITY DEFINER
functions.  The purpose of this change is to ensure that user-defined
functions used in index definitions cannot acquire the privileges of a
superuser account that is performing routine maintenance.  While a function
used in an index is supposed to be IMMUTABLE and thus not able to do anything
very interesting, there are several easy ways around that restriction; and
even if we could plug them all, there would remain a risk of reading sensitive
information and broadcasting it through a covert channel such as CPU usage.

To prevent bypassing this security measure, execution of SET SESSION
AUTHORIZATION and SET ROLE is now forbidden within a SECURITY DEFINER context.

Thanks to Itagaki Takahiro for reporting this vulnerability.

Security: CVE-2007-6600
2008-01-03 21:23:15 +00:00
8af31d56f4 Add:
> * Allow multiple identical NOTIFY events to always be communicated to the
>   client, rather than sent as a single notification to the listener
2008-01-03 18:47:44 +00:00
86b322b16f Fix invalid ipv6 address in example. Per doc comment 7211. 2008-01-02 19:53:13 +00:00
9098ab9e32 Update copyrights in source tree to 2008. 2008-01-01 19:46:01 +00:00