aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
* Release notes for 9.3.5, 9.2.9, 9.1.14, 9.0.18, 8.4.22.Tom Lane2014-07-21
|
* Fix xreflabel for hot_standby_feedback.Tom Lane2014-07-19
| | | | Rather remarkable that this has been wrong since 9.1 and nobody noticed.
* Limit pg_upgrade authentication advice to always-secure techniques.Noah Misch2014-07-18
| | | | | | | ~/.pgpass is a sound choice everywhere, and "peer" authentication is safe on every platform it supports. Cease to recommend "trust" authentication, the safety of which is deeply configuration-specific. Back-patch to 9.0, where pg_upgrade was introduced.
* Reset master xmin when hot_standby_feedback disabled.Simon Riggs2014-07-15
| | | | | | If walsender has xmin of standby then ensure we reset the value to 0 when we change from hot_standby_feedback=on to hot_standby_feedback=off.
* doc: small fixes for REINDEX reference pagePeter Eisentraut2014-07-14
| | | | From: Josh Kupershmidt <schmiddy@gmail.com>
* Remove obsolete example of CSV log file name from log_filename document.Fujii Masao2014-06-26
| | | | | | | | | | | | | | 7380b63 changed log_filename so that epoch was not appended to it when no format specifier is given. But the example of CSV log file name with epoch still left in log_filename document. This commit removes such obsolete example. This commit also documents the defaults of log_directory and log_filename. Backpatch to all supported versions. Christoph Berg
* Fix documentation template for CREATE TRIGGER.Kevin Grittner2014-06-21
| | | | | | | | | By using curly braces, the template had specified that one of "NOT DEFERRABLE", "INITIALLY IMMEDIATE", or "INITIALLY DEFERRED" was required on any CREATE TRIGGER statement, which is not accurate. Change to square brackets makes that optional. Backpatch to 9.1, where the error was introduced.
* Secure Unix-domain sockets of "make check" temporary clusters.Noah Misch2014-06-14
| | | | | | | | | | | | | | | | | Any OS user able to access the socket can connect as the bootstrap superuser and proceed to execute arbitrary code as the OS user running the test. Protect against that by placing the socket in a temporary, mode-0700 subdirectory of /tmp. The pg_regress-based test suites and the pg_upgrade test suite were vulnerable; the $(prove_check)-based test suites were already secure. Back-patch to 8.4 (all supported versions). The hazard remains wherever the temporary cluster accepts TCP connections, notably on Windows. As a convenient side effect, this lets testing proceed smoothly in builds that override DEFAULT_PGSOCKET_DIR. Popular non-default values like /var/run/postgresql are often unwritable to the build user. Security: CVE-2014-0067
* Document permissions needed for pg_database_size and pg_tablespace_size.Tom Lane2014-05-08
| | | | | | | Back in 8.3, we installed permissions checks in these functions (see commits 8bc225e7990a and cc26599b7206). But we forgot to document that anywhere in the user-facing docs; it did get mentioned in the 8.3 release notes, but nobody's looking at that any more. Per gripe from Suya Huang.
* Fix documentation about joining pg_locks to other views.Tom Lane2014-04-03
| | | | | | | | | | | The advice to join to pg_prepared_xacts via the transaction column was not updated when the transaction column was replaced by virtualtransaction. Since it's not quite obvious how to do that join, give an explicit example. For consistency also give an example for the adjacent case of joining to pg_stat_activity. And link-ify the view references too, just because we can. Per bug #9840 from Alexey Bashtanov. Michael Paquier and Tom Lane
* Fix documentation about size of interval type.Tom Lane2014-04-03
| | | | | | It's been 16 bytes, not 12, for ages. This was fixed in passing in HEAD (commit 146604ec), but as a factual error it should have been back-patched. Per gripe from Tatsuhito Kasahara.
* Revert "Secure Unix-domain sockets of "make check" temporary clusters."Noah Misch2014-03-29
| | | | | About half of the buildfarm members use too-long directory names, strongly suggesting that this approach is a dead end.
* Secure Unix-domain sockets of "make check" temporary clusters.Noah Misch2014-03-29
| | | | | | | | | | | | | | | | | | | | | Any OS user able to access the socket can connect as the bootstrap superuser and in turn execute arbitrary code as the OS user running the test. Protect against that by placing the socket in the temporary data directory, which has mode 0700 thanks to initdb. Back-patch to 8.4 (all supported versions). The hazard remains wherever the temporary cluster accepts TCP connections, notably on Windows. Attempts to run "make check" from a directory with a long name will now fail. An alternative not sharing that problem was to place the socket in a subdirectory of /tmp, but that is only secure if /tmp is sticky. The PG_REGRESS_SOCK_DIR environment variable is available as a workaround when testing from long directory paths. As a convenient side effect, this lets testing proceed smoothly in builds that override DEFAULT_PGSOCKET_DIR. Popular non-default values like /var/run/postgresql are often unwritable to the build user. Security: CVE-2014-0067
* Document platform-specificity of unix_socket_permissions.Noah Misch2014-03-29
| | | | Back-patch to 8.4 (all supported versions).
* Fix typos in pg_basebackup documentationMagnus Hagander2014-03-25
| | | | Joshua Tolley
* Release notes for 9.3.4, 9.2.8, 9.1.13, 9.0.17, 8.4.21.Tom Lane2014-03-17
|
* Fix name of syslog_ident GUC in docs.Heikki Linnakangas2014-03-07
| | | | Michael Paquier
* Last-minute updates for release notes.Tom Lane2014-02-17
| | | | | | Add entries for security issues. Security: CVE-2014-0060 through CVE-2014-0067
* Document risks of "make check" in the regression testing instructions.Tom Lane2014-02-17
| | | | | | | | | | | | | | | | | | | | Since the temporary server started by "make check" uses "trust" authentication, another user on the same machine could connect to it as database superuser, and then potentially exploit the privileges of the operating-system user who started the tests. We should change the testing procedures to prevent this risk; but discussion is required about the best way to do that, as well as more testing than is practical for an undisclosed security problem. Besides, the same issue probably affects some user-written test harnesses. So for the moment, we'll just warn people against using "make check" when there are untrusted users on the same machine. In passing, remove some ancient advice that suggested making the regression testing subtree world-writable if you'd built as root. That looks dangerously insecure in modern contexts, and anyway we should not be encouraging people to build Postgres as root. Security: CVE-2014-0067
* Document security implications of check_function_bodies.Noah Misch2014-02-17
| | | | Back-patch to 8.4 (all supported versions).
* Prevent privilege escalation in explicit calls to PL validators.Noah Misch2014-02-17
| | | | | | | | | | | | | | The primary role of PL validators is to be called implicitly during CREATE FUNCTION, but they are also normal functions that a user can call explicitly. Add a permissions check to each validator to ensure that a user cannot use explicit validator calls to achieve things he could not otherwise achieve. Back-patch to 8.4 (all supported versions). Non-core procedural language extensions ought to make the same two-line change to their own validators. Andres Freund, reviewed by Tom Lane and Noah Misch. Security: CVE-2014-0061
* Shore up ADMIN OPTION restrictions.Noah Misch2014-02-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Granting a role without ADMIN OPTION is supposed to prevent the grantee from adding or removing members from the granted role. Issuing SET ROLE before the GRANT bypassed that, because the role itself had an implicit right to add or remove members. Plug that hole by recognizing that implicit right only when the session user matches the current role. Additionally, do not recognize it during a security-restricted operation or during execution of a SECURITY DEFINER function. The restriction on SECURITY DEFINER is not security-critical. However, it seems best for a user testing his own SECURITY DEFINER function to see the same behavior others will see. Back-patch to 8.4 (all supported versions). The SQL standards do not conflate roles and users as PostgreSQL does; only SQL roles have members, and only SQL users initiate sessions. An application using PostgreSQL users and roles as SQL users and roles will never attempt to grant membership in the role that is the session user, so the implicit right to add or remove members will never arise. The security impact was mostly that a role member could revoke access from others, contrary to the wishes of his own grantor. Unapproved role member additions are less notable, because the member can still largely achieve that by creating a view or a SECURITY DEFINER function. Reviewed by Andres Freund and Tom Lane. Reported, independently, by Jonas Sundman and Noah Misch. Security: CVE-2014-0060
* Release notes for 9.3.3, 9.2.7, 9.1.12, 9.0.16, 8.4.20.Tom Lane2014-02-16
|
* Update regression testing instructions.Tom Lane2014-02-14
| | | | | | | | | | | | | This documentation never got the word about the existence of check-world or installcheck-world. Revise to recommend use of those, and document all the subsidiary test suites. Do some minor wordsmithing elsewhere, too. In passing, remove markup related to generation of plain-text regression test instructions, since we don't do that anymore. Back-patch to 9.1 where check-world was added. (installcheck-world exists in 9.0; but since check-world doesn't, this patch would need additional work to cover that branch, and it doesn't seem worth the effort.)
* Suggest shell here-documents instead of psql -c for multiple commands.Tom Lane2014-02-14
| | | | | | The documentation suggested using "echo | psql", but not the often-superior alternative of a here-document. Also, be more direct about suggesting that people avoid -c for multiple commands. Per discussion.
* Improve cross-references between minor version release notes.Tom Lane2014-02-12
| | | | | | | | | | | | We have a practice of providing a "bread crumb" trail between the minor versions where the migration section actually tells you to do something. Historically that was just plain text, eg, "see the release notes for 9.2.4"; but if you're using a browser or PDF reader, it's a lot nicer if it's a live hyperlink. So use "<xref>" instead. Any argument against doing this vanished with the recent decommissioning of plain-text release notes. Vik Fearing
* Don't generate plain-text HISTORY and src/test/regress/README anymore.Tom Lane2014-02-10
| | | | | | | | | | | | | | | | | | | | | Providing this information as plain text was doubtless worth the trouble ten years ago, but it seems likely that hardly anyone reads it in this format anymore. And the effort required to maintain these files (in the form of extra-complex markup rules in the relevant parts of the SGML documentation) is significant. So, let's stop doing that and rely solely on the other documentation formats. Per discussion, the plain-text INSTALL instructions might still be worth their keep, so we continue to generate that file. Rather than remove HISTORY and src/test/regress/README from distribution tarballs entirely, replace them with simple stub files that tell the reader where to find the relevant documentation. This is mainly to avoid possibly breaking packaging recipes that expect these files to exist. Back-patch to all supported branches, because simplifying the markup requirements for release notes won't help much unless we do it in all branches.
* Update copyright for 2014Bruce Momjian2014-01-07
| | | | | Update all files in head, and files COPYRIGHT and legal.sgml in all back branches.
* Fix ancient docs/comments thinko: XID comparison is mod 2^32, not 2^31.Tom Lane2013-12-12
| | | | Pointed out by Gianni Ciolli.
* Update release notes for 9.3.2, 9.2.6, 9.1.11, 9.0.15, 8.4.19.Tom Lane2013-12-02
|
* Documentation fix for ecpg.Michael Meskes2013-11-27
| | | | The latest fixes removed a limitation that was still in the docs, so Zoltan updated the docs, too.
* Fix typo in release note.Fujii Masao2013-11-27
| | | | | | Backpatch to 9.1. Josh Kupershmidt
* Clarify CREATE FUNCTION documentation about handling of typmods.Tom Lane2013-11-13
| | | | | The previous text was a bit misleading, as well as unnecessarily vague about what information would be discarded. Per gripe from Craig Skinner.
* Prevent creating window functions with default arguments.Tom Lane2013-11-06
| | | | | | | Insertion of default arguments doesn't work for window functions, which is likely to cause a crash at runtime if the implementation code doesn't check the number of actual arguments carefully. It doesn't seem worth working harder than this for pre-9.2 branches.
* Improve the error message given for modifying a window with frame clause.Tom Lane2013-11-05
| | | | | | | | | | | | | | For rather inscrutable reasons, SQL:2008 disallows copying-and-modifying a window definition that has any explicit framing clause. The error message we gave for this only made sense if the referencing window definition itself contains an explicit framing clause, which it might well not. Moreover, in the context of an OVER clause it's not exactly obvious that "OVER (windowname)" implies copy-and-modify while "OVER windowname" does not. This has led to multiple complaints, eg bug #5199 from Iliya Krapchatov. Change to a hopefully more intelligible error message, and in the case where we have just "OVER (windowname)", add a HINT suggesting that omitting the parentheses will fix it. Also improve the related documentation. Back-patch to all supported branches.
* doc: Remove i18ngurus.com linkPeter Eisentraut2013-10-21
| | | | | The web site is dead, and the Wayback Machine shows that it didn't have much useful content before.
* docs: correct 9.1 and 9.2 release note mention of timeline switch fixBruce Momjian2013-10-15
| | | | | | Backpatch through 9.1. KONDO Mitsumasa
* doc: fix typo in release notesBruce Momjian2013-10-09
| | | | | | Backpatch through 8.4 Per suggestion by Amit Langote
* Revert "Document support for VPATH builds of extensions."Peter Eisentraut2013-10-07
| | | | This reverts commit 6ed3c5f7b2846be9e176ea1c99b2d45bba0d6972.
* docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9.3.1Bruce Momjian2013-10-07
|
* Document support for VPATH builds of extensions.Andrew Dunstan2013-10-06
| | | | Cédric Villemain and me.
* doc: Correct psycopg URLPeter Eisentraut2013-10-02
|
* Don't fail for bad GUCs in CREATE FUNCTION with check_function_bodies off.Tom Lane2013-09-03
| | | | | | | | | | | | | | | | | | | | | | | The previous coding attempted to activate all the GUC settings specified in SET clauses, so that the function validator could operate in the GUC environment expected by the function body. However, this is problematic when restoring a dump, since the SET clauses might refer to database objects that don't exist yet. We already have the parameter check_function_bodies that's meant to prevent forward references in function definitions from breaking dumps, so let's change CREATE FUNCTION to not install the SET values if check_function_bodies is off. Authors of function validators were already advised not to make any "context sensitive" checks when check_function_bodies is off, if indeed they're checking anything at all in that mode. But extend the documentation to point out the GUC issue in particular. (Note that we still check the SET clauses to some extent; the behavior with !check_function_bodies is now approximately equivalent to what ALTER DATABASE/ROLE have been doing for awhile with context-dependent GUCs.) This problem can be demonstrated in all active branches, so back-patch all the way.
* Fix relfrozenxid query in docs to include TOAST tables.Andrew Dunstan2013-09-02
| | | | | | | The original query ignored TOAST tables which could result in tables needing a vacuum not being reported. Backpatch to all live branches.
* doc: Fix typos in conversion names.Robert Haas2013-07-19
| | | | David Christensen
* Fixed incorrect description of EXEC SQL VAR command.Michael Meskes2013-07-12
| | | | Thanks to MauMau <maumau307@gmail.com> for finding and fixing this.
* pg_upgrade: document possible pg_hba.conf optionsBruce Momjian2013-07-11
| | | | | | | | Previously, pg_upgrade docs recommended using .pgpass if using MD5 authentication to avoid being prompted for a password. Turns out pg_ctl never prompts for a password, so MD5 requires .pgpass --- document that. Also recommend 'peer' for authentication too. Backpatch back to 9.1.
* Remove stray | characterMagnus Hagander2013-07-05
| | | | Erikjan Rijkers
* Mention extra_float_digits in floating point docsAlvaro Herrera2013-07-02
| | | | | | | | | | | Make it easier for readers of the FP docs to find out about possibly truncated values. Per complaint from Tom Duffey in message F0E0F874-C86F-48D1-AA2A-0C5365BF5118@trillitech.com Author: Albe Laurenz Reviewed by: Abhijit Menon-Sen
* Tweak wording in sequence-function docs to avoid PDF build failures.Tom Lane2013-06-27
| | | | | | | | | | | | | | Adjust the wording in the first para of "Sequence Manipulation Functions" so that neither of the link phrases in it break across line boundaries, in either A4- or US-page-size PDF output. This fixes a reported build failure for the 9.3beta2 A4 PDF docs, and future-proofs this particular para against causing similar problems in future. (Perhaps somebody will fix this issue in the SGML/TeX documentation tool chain someday, but I'm not holding my breath.) Back-patch to all supported branches, since the same problem could rise up to bite us in future updates if anyone changes anything earlier than this in func.sgml.
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-07 15:36:58 +0000