6345 Commits (f44391b0a02870f877c2775ce706201fc1ebf33c)

Author	SHA1	Message	Date
Bruce Momjian	f44391b0a0	Document issues with non-default tablespaces and pg_dumpall restores. ... Backpatch documentation addition to 8.1.X.	20 years ago
Bruce Momjian	401ffe0555	Backpatch documentation additions for PL language choice and ... regex_replace() to 8.1.X.	20 years ago
Bruce Momjian	8a507aeaeb	Rename in release notes: Mac -> OS/X, Intel to x86: ... Fix for OS/X Bonjour on x86 systems (Ashley Clark)	20 years ago
Tom Lane	3f6b5e21c8	Update release notes for upcoming releases.	20 years ago
Tom Lane	7f615cab57	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	3d4dc1acf5	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
Bruce Momjian	e720382441	Stamp 8.1.4, except configure/configure.in.	20 years ago
Bruce Momjian	289f10c809	Update release notes for 8.1.4.	20 years ago
Bruce Momjian	95d8b6a7b4	Backpatch FAQs to 8.1.X.	20 years ago
Bruce Momjian	4aec5303f0	Update pg_dump version wording.	20 years ago
Bruce Momjian	dfc2fc2522	Mention version portability of pg_dump.	20 years ago
Bruce Momjian	21138b5e59	Suggest Win32 users user E'' strings and double backslashes used for ... patch separators in COPY. Backpatch doubleing backslashes suggestion to 8.1.	20 years ago
Bruce Momjian	6b46ec2707	Mention "syntax" error as not logged by log_statement. ... Backpatch.	20 years ago
Bruce Momjian	65f1a7a8dc	Document that errors are not output by log_statement (was they were in ... 8.0), and add as suggestion to use log_min_error_statement for this purpose. I also fixed the code so the first EXECUTE has it's prepare, rather than the last which is what was in the current code. Also remove "protocol" prefix for SQL EXECUTE output because it is not accurate. Backpatch to 8.1.X.	20 years ago
Bruce Momjian	dd8d1b1fbd	Document that pg_dump -d/-D prevents invalid data from canceling the ... entire table load.	20 years ago
Bruce Momjian	9b83454f7f	Update AIX FAQ: ... At any rate, here's a revision to CVS HEAD to reflect some changes by myself and by Seneca Cunningham for the AIX FAQ. It touches on the following issues: 1. memcpy pointer patch for dynahash.c 2. AIX memory management, which can, for 32 bit cases, bite people quite unexpectedly... Chris Browne	20 years ago
Bruce Momjian	a5884d5dc8	Updated Japanese FAQ, version 2. ... J.Kuwamura	20 years ago
Bruce Momjian	5052aa2edb	Update Japanese FAQ, backpatch. ... J.Kuwamura	20 years ago
Bruce Momjian	cc1b59c951	Oops, sysctl, not sysconf, for FreeBSD.	20 years ago
Bruce Momjian	e860973aed	More FreeBSD jail wording improvements.	20 years ago
Bruce Momjian	493eea649c	Add documentation about running postmasters in FreeBSD jails (use ... separate users).	20 years ago
Bruce Momjian	36d5976f9e	There is updated Russian translation of the FAQ in the attachment. ... Victor Vislobokov	20 years ago
Bruce Momjian	69ab90c775	Update AIX FAQ to show readline options more clearly. ... Backpatch FAQ's to 8.1.X.	20 years ago
Tom Lane	fdc28fdcfa	Disable full_page_writes, because turning it off risks causing crash-recovery ... failures even when the hardware and OS did nothing wrong. Per recent analysis of a problem report from Alex Bahdushka. For the moment I've just diked out the test of the parameter, rather than removing the GUC infrastructure and documentation, in case we conclude that there's something salvageable there. There seems no chance of it being resurrected in the 8.1 branch though.	20 years ago
Tom Lane	0a5c6fadf4	Remove somebody's flight of fancy about an UPDATE with ORDER BY and LIMIT.	20 years ago
Bruce Momjian	2c620740bd	Appended is a small documentation patch that adds a note to the CREATE ... ROLE page, based on what Tom Lane told me here: http://archives.postgresql.org/pgsql-general/2005-11/msg00998.php Joachim Wieland	20 years ago
Tom Lane	69f69808c5	Fix ancient error in large objects usage example: overwrite() subroutine ... was opening with INV_READ flag and then writing. Prior to 8.1 the backend did not reject this, but now it does.	20 years ago
Bruce Momjian	5e4bf929b3	Update OS X shared memory documentation for 10.3.9 and later to use ... /etc/sysctl.conf. Chris Campbell	20 years ago
Bruce Momjian	006bd450fe	Mark tsearch2 item as Tom's, not Teodor's.	20 years ago
Bruce Momjian	15516c5f0b	Update FAQ_DEV text file.	20 years ago
Bruce Momjian	88a4314bb1	Update patch generation instructions. ... Robert Treat	20 years ago
Bruce Momjian	e559dba846	Update Japanese FAQ, backpatched to 8.1.X.	20 years ago
Bruce Momjian	6853e34132	Add pg_service.conf documentation for libpq.	20 years ago
Bruce Momjian	3952eecd4a	Fix computation of sample table size.	20 years ago
Bruce Momjian	032858216c	Backpatch FAQ changes to 8.1.X.	20 years ago
Bruce Momjian	39825338b4	Mention that the archive history file has the wal start/stop file names.	20 years ago
Tom Lane	ef434ebfbc	Update release notes.	20 years ago
Tom Lane	b71e2bb122	Fix broken markup.	20 years ago
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.	20 years ago
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	20 years ago
Bruce Momjian	34d9bbee4d	Stamp releases for 2006-02-14 release	20 years ago
Bruce Momjian	003daafb0d	Fix release item ordering.	20 years ago
Bruce Momjian	12ea69aaf5	Update back branch release notes.	20 years ago
Bruce Momjian	d9dafcc5d6	Fix release markup.	20 years ago
Bruce Momjian	a318438fb3	Stamp 8.1.3, but exclude configure.in/configure change.	20 years ago
Bruce Momjian	3a9c81e3e9	Update release notes for 8.1.3.	20 years ago
Tom Lane	f527f082c5	Reject out-of-range dates in date_in(). ... Kris Jurka	20 years ago
Bruce Momjian	c75c372c58	Fix typo in configuration docs. ... Devrim GUNDUZ	20 years ago
Bruce Momjian	3bf6284f10	Update PL/pgSQL trigger example to be clearer about how to "merge" data ... into a table. Jim C. Nasby	20 years ago
Bruce Momjian	4a651c9705	Update EXPLAIN wording for GEQO usage.	20 years ago