5524 Commits (0e9888b90d41bdb95ddbc1f4b22d61ba6bf5fdc1)

Author	SHA1	Message	Date
Magnus Hagander	0e9888b90d	Fix invalid ipv6 address in example. Per doc comment 7211.	19 years ago
Tatsuo Ishii	2f5a7506c6	Fix "Overall Page Layout" table. The second row should be ItemIdData, not ... ItemPointerData.	19 years ago
Tom Lane	ef00409020	Make archive recovery always start a new timeline, rather than only when a ... recovery stop time was used. This avoids a corner-case risk of trying to overwrite an existing archived copy of the last WAL segment, and seems simpler and cleaner all around than the original definition. Per example from Jon Colverson and subsequent analysis by Simon.	19 years ago
Tom Lane	038f7e4afb	Update release notes for last-minute fix.	19 years ago
Tom Lane	d620f2d383	Fix markup that doesn't work in back branches.	19 years ago
Tom Lane	42765a29f9	Minor editorialization on release notes.	19 years ago
Bruce Momjian	37ac2f6d1f	Stamp releases 8.2.5, 8.1.10, 8.0.14, 7.4.18, 7.3.20. ... Update FAQs for 8.2.5.	19 years ago
Bruce Momjian	30099c28f0	Stamp	19 years ago
Tom Lane	94dc2d8e3b	Fix array_dims() example to be consistent with the data previously shown. ... Christian Rossow	19 years ago
Peter Eisentraut	e7933588eb	Fix spurious German index entry	19 years ago
Magnus Hagander	8e0bcdc855	Document that CLUSTER breaks MVCC visibility rules. ... (Not needed in cvs head, because CLUSTER itself is fixed there) Heikki Linnakangas	19 years ago
Neil Conway	d221ef7bdf	Fix newly-introduced documentation typo.	19 years ago
Tom Lane	cfe1b04c66	Fix markup. ... Security: CVE-2007-2138	19 years ago
Tom Lane	566331a2e9	Support explicit placement of the temporary-table schema within search_path. ... This is needed to allow a security-definer function to set a truly secure value of search_path. Without it, a malicious user can use temporary objects to execute code with the privileges of the security-definer function. Even pushing the temp schema to the back of the search path is not quite good enough, because a function or operator at the back of the path might still capture control from one nearer the front due to having a more exact datatype match. Hence, disable searching the temp schema altogether for functions and operators. Security: CVE-2007-2138	19 years ago
Bruce Momjian	77be1e891d	Release wording updates for releases 8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19.	19 years ago
Bruce Momjian	447b2b9220	Update FAQ to mention most recent release for releases ... 8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19.	19 years ago
Bruce Momjian	416dcc4927	Stamp releases 8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19.	19 years ago
Bruce Momjian	a7ce947b63	Release note updates for 8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19.	19 years ago
Tom Lane	967d6add8d	Arrange to install a "posixrules" entry in our timezone database, so that ... POSIX-style timezone specs that don't exactly match any database entry will be treated as having correct USA DST rules. Also, document that this can be changed if you want to use some other DST rules with a POSIX zone spec. We could consider changing localtime.c's TZDEFRULESTRING, but since that facility can only deal with one DST transition rule, it seems fairly useless now; might as well just plan to override it using a "posixrules" entry. Backpatch as far as 8.0. There isn't much we can do in 7.x ... either your libc gets it right, or it doesn't.	20 years ago
Bruce Momjian	dc80902bcc	Stamp releases notes for 8.2.3, 8.1.8, 8.0.12.	20 years ago
Bruce Momjian	8cbd1c3ba8	Stamp releases 8.2.3, 8.1.8, 8.0.12. No release notes yet.	20 years ago
Neil Conway	2f92bea3a5	Reword suggestion that libpq.dll be installed in WINNT\SYSTEM32 under ... Windows. Per Magnus Hagander, this is not recommended.	20 years ago
Tom Lane	d724689b73	Stamp release 8.0.11. ... Security: CVE-2007-0555, CVE-2007-0556	20 years ago
Tom Lane	384f05d55a	Update release notes for security-related releases in all active branches. ... Security: CVE-2007-0555, CVE-2007-0556	20 years ago
Tom Lane	3d5f28671a	Links to GUC variables from HISTORY don't work in back branches...	20 years ago
Bruce Momjian	a05e93ed52	Fix markup because older releases couldn't link to the reference section.	20 years ago
Tom Lane	ccd743ef5d	Minor copy-editing for release note updates.	20 years ago
Bruce Momjian	e0f20bbe44	Stamp release 8.0.10.	20 years ago
Bruce Momjian	1f503f27d5	Create release notes for 8.0.10.	20 years ago
Tom Lane	1eaf9ef62a	Document the recently-understood hazard that a rollback can release row-level ... locks that logically should not be released, because when a subtransaction overwrites XMAX all knowledge of the previous lock state is lost. It seems unlikely that we will be able to fix this before 8.3...	20 years ago
Tom Lane	db9ebafca1	Update release notes for SQL functions vs triggers fix.	20 years ago
Tom Lane	b6a71905d3	A bit of copy-editing on back-branch release notes.	20 years ago
Bruce Momjian	bc0fa10440	Stamp releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5.	20 years ago
Bruce Momjian	b07bda6312	Update release notes for releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5.	20 years ago
Tom Lane	4d3760f674	date_trunc also accepts 'quarter'. Noted by Yoshihisa Nakano.	20 years ago
Alvaro Herrera	632db651cb	Fix confusion between COPY FROM and COPY TO, per Gavin Sharry and Arul Shaji.	20 years ago
Tom Lane	f39fc4769e	Stamp release 8.0.8.	20 years ago
Tom Lane	e35c0aee33	Update release notes for upcoming releases.	20 years ago
Bruce Momjian	29dd673a94	Stamp releases 7.3.15, 7.4.13, and 8.0.8.	20 years ago
Tom Lane	94dec9114b	Modify libpq's string-escaping routines to be aware of encoding considerations ... and standard_conforming_strings. The encoding changes are needed for proper escaping in multibyte encodings, as per the SQL-injection vulnerabilities noted in CVE-2006-2313 and CVE-2006-2314. Concurrent fixes are being applied to the server to ensure that it rejects queries that may have been corrupted by attempted SQL injection, but this merely guarantees that unpatched clients will fail rather than allow injection. An actual fix requires changing the client-side code. While at it we have also fixed these routines to understand about standard_conforming_strings, so that the upcoming changeover to SQL-spec string syntax can be somewhat transparent to client code. Since the existing API of PQescapeString and PQescapeBytea provides no way to inform them which settings are in use, these functions are now deprecated in favor of new functions PQescapeStringConn and PQescapeByteaConn. The new functions take the PGconn to which the string will be sent as an additional parameter, and look inside the connection structure to determine what to do. So as to provide some functionality for clients using the old functions, libpq stores the latest encoding and standard_conforming_strings values received from the backend in static variables, and the old functions consult these variables. This will work reliably in clients using only one Postgres connection at a time, or even multiple connections if they all use the same encoding and string syntax settings; which should cover many practical scenarios. Clients that use homebrew escaping methods, such as PHP's addslashes() function or even hardwired regexp substitution, will require extra effort to fix :-(. It is strongly recommended that such code be replaced by use of PQescapeStringConn/PQescapeByteaConn if at all feasible.	20 years ago
Tom Lane	9bc62ddd5f	Add a new GUC parameter backslash_quote, which determines whether the SQL ... parser will allow "\'" to be used to represent a literal quote mark. The "\'" representation has been deprecated for some time in favor of the SQL-standard representation "''" (two single quote marks), but it has been used often enough that just disallowing it immediately won't do. Hence backslash_quote allows the settings "on", "off", and "safe_encoding", the last meaning to allow "\'" only if client_encoding is a valid server encoding. That is now the default, and the reason is that in encodings such as SJIS that allow 0x5c (ASCII backslash) to be the last byte of a multibyte character, accepting "\'" allows SQL-injection attacks as per CVE-2006-2314 (further details will be published after release). The "on" setting is available for backward compatibility, but it must not be used with clients that are exposed to untrusted input. Thanks to Akio Ishida and Yasuo Ohgaki for identifying this security issue.	20 years ago
Tom Lane	2d584b5c1b	Update release notes.	21 years ago
Bruce Momjian	9bb401cd73	Update FAQ latest version	21 years ago
Bruce Momjian	5ae9c6138b	Stamp releases for 2006-02-14 release	21 years ago
Bruce Momjian	dfa879bc98	Update release notes for 2006-02-14 release	21 years ago
Tom Lane	a14302080f	Reject out-of-range dates in date_in(). ... Kris Jurka	21 years ago
Tom Lane	e82858f013	Release-note updates and copy editing.	21 years ago
Bruce Momjian	0add52b4f6	New pgcrypto item wording.	21 years ago
Bruce Momjian	240fb6dd4f	Wording improvements.	21 years ago
Bruce Momjian	4011909a02	Improve markup.	21 years ago