aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Document effect of constant folding on CASE.Noah Misch2013-06-26
| | | | | | Back-patch to all supported versions. Laurenz Albe
* Update CREATE FUNCTION documentation about argument namesPeter Eisentraut2013-06-19
| | | | More languages than PL/pgSQL actually support parameter names.
* Fix docs on lock level for ALTER TABLE VALIDATESimon Riggs2013-06-18
| | | | | | | | | ALTER TABLE .. VALIDATE CONSTRAINT previously gave incorrect details about lock levels and therefore incomplete reasons to use the option. Initial bug report and fix from Marko Tiikkaja Reworded by me to include comments by Kevin Grittner
* Improve description of loread/lowrite.Robert Haas2013-06-12
| | | | Patch by me, reviewed by Tatsuo Ishii.
* Add description that loread()/lowrite() are corresponding toTatsuo Ishii2013-06-11
| | | | lo_read()/lo_write() in libpq to avoid confusion.
* Remove ALTER DEFAULT PRIVILEGES' requirement of schema CREATE permissions.Tom Lane2013-06-09
| | | | | | | | Per discussion, this restriction isn't needed for any real security reason, and it seems to confuse people more often than it helps them. It could also result in some database states being unrestorable. So just drop it. Back-patch to 9.0, where ALTER DEFAULT PRIVILEGES was introduced.
* Correct the documentation of pg_rewrite.ev_attr.Kevin Grittner2013-06-07
| | | | | | | | It claimed the value was always zero; it is really always -1. Per report from Hari Babu backpatch 734fbbd1d2d1babfbd195414e2445024ad549ae3 to 8.4
* Minor docs wordsmithing.Tom Lane2013-06-07
| | | | | | | Swap the order of a couple of phrases to clarify what the adjective "subsequent" applies to. Joshua Tolley
* Documentation fix for ALTER TYPE .. RENAMEStephen Frost2013-05-27
| | | | | | | | | | | | The documentation for ALTER TYPE .. RENAME claimed to support a RESTRICT/CASCADE option at the 'type' level, which wasn't implemented and doesn't make a whole lot of sense to begin with. What is supported, and previously undocumented, is ALTER TYPE .. RENAME ATTRIBUTE .. RESTRICT/CASCADE. I've updated the documentation and back-patched this to 9.1 where it was first introduced.
* docs: log_line_prefix session id fixBruce Momjian2013-05-04
| | | | | | | | | Restore 4-byte designation for docs. Fix 9.3 doc query to properly pad to four digits. Backpatch to all active branches Per suggestions from Ian Lawrence Barwick
* doc: fix log_line_prefix session_id %c itemBruce Momjian2013-05-04
| | | | | | Backpatch to 9.1 and earlier Report from Ian Lawrence Barwick
* Improve documentation about the relationship of extensions and schemas.Tom Lane2013-04-04
| | | | | There's been some confusion expressed about this point, so clarify. Extended version of a patch by David Wheeler.
* doc: Fix number of columns in tablePeter Eisentraut2013-04-04
|
* Update release notes for 9.2.4, 9.1.9, 9.0.13, 8.4.17.Tom Lane2013-04-01
| | | | Security: CVE-2013-1899, CVE-2013-1901
* Document encode(bytea, 'escape')'s behavior correctly.Tom Lane2013-03-28
| | | | | | | | | I changed this in commit fd15dba543247eb1ce879d22632b9fdb4c230831, but missed the fact that the SGML documentation of the function specified exactly what it did. Well, one of the two places where it's specified documented that --- probably I looked at the other place and thought nothing needed to be done. Sync the two places where encode() and decode() are described.
* Don't put <indexterm> before <term> in <varlistentry> items.Tom Lane2013-03-23
| | | | | | | | Doing that results in a broken index entry in PDF output. We had only a few like that, which is probably why nobody noticed before. Standardize on putting the <term> first. Josh Kupershmidt
* Improve documentation of EXTRACT(WEEK).Tom Lane2013-03-18
| | | | | | | | The docs showed that early-January dates can be considered part of the previous year for week-counting purposes, but failed to say explicitly that late-December dates can also be considered part of the next year. Fix that, and add a cross-reference to the "isoyear" field. Per bug #7967 from Pawel Kobylak.
* doc: Awkward phrasing fixPeter Eisentraut2013-03-03
| | | | Josh Kupershmidt
* doc: Fix markup typoPeter Eisentraut2013-02-25
|
* doc: Remove PostgreSQL version number from xml2 deprecation noticePeter Eisentraut2013-02-24
| | | | It is obviously no longer true.
* Prevent execution of enum_recv() from SQL.Tom Lane2013-02-04
| | | | | | | | | | | | | | | | | This function was misdeclared to take cstring when it should take internal. This at least allows crashing the server, and in principle an attacker might be able to use the function to examine the contents of server memory. The correct fix is to adjust the system catalog contents (and fix the regression tests that should have caught this but failed to). However, asking users to correct the catalog contents in existing installations is a pain, so as a band-aid fix for the back branches, install a check in enum_recv() to make it throw error if called with a cstring argument. We will later revert this in HEAD in favor of correcting the catalogs. Our thanks to Sumit Soni (via Secunia SVCRP) for reporting this issue. Security: CVE-2013-0255
* Update release notes for 9.2.3, 9.1.8, 9.0.12, 8.4.16, 8.3.23.Tom Lane2013-02-04
|
* Reset vacuum_defer_cleanup_age to PGC_SIGHUP.Simon Riggs2013-02-04
| | | | Revert commit 84725aa5efe11688633b553e58113efce4181f2e
* Mark vacuum_defer_cleanup_age as PGC_POSTMASTER.Simon Riggs2013-02-02
| | | | Following bug analysis of #7819 by Tom Lane
* DROP OWNED: don't try to drop tablespaces/databasesAlvaro Herrera2013-01-28
| | | | | | | | | | | | | | | | | My "fix" for bugs #7578 and #6116 on DROP OWNED at fe3b5eb08a1 not only misstated that it applied to REASSIGN OWNED (which it did not affect), but it also failed to fix the problems fully, because I didn't test the case of owned shared objects. Thus I created a new bug, reported by Thomas Kellerer as #7748, which would cause DROP OWNED to fail with a not-for-user-consumption error message. The code would attempt to drop the database, which not only fails to work because the underlying code does not support that, but is a pretty dangerous and undesirable thing to be doing as well. This patch fixes that bug by having DROP OWNED only attempt to process shared objects when grants on them are found, ignoring ownership. Backpatch to 8.3, which is as far as the previous bug was backpatched.
* doc: backpatch MVCC wording improvements to 9.1Bruce Momjian2013-01-25
| | | | Per request from Thom Brown
* Make pg_dump exclude unlogged table data on hot standby slavesMagnus Hagander2013-01-25
| | | | Noted by Joe Van Dyk
* Fix SPI documentation for new handling of ExecutorRun's count parameter.Tom Lane2013-01-24
| | | | | | | | | | | | | | Since 9.0, the count parameter has only limited the number of tuples actually returned by the executor. It doesn't affect the behavior of INSERT/UPDATE/DELETE unless RETURNING is specified, because without RETURNING, the ModifyTable plan node doesn't return control to execMain.c for each tuple. And we only check the limit at the top level. While this behavioral change was unintentional at the time, discussion of bug #6572 led us to the conclusion that we prefer the new behavior anyway, and so we should just adjust the docs to match rather than change the code. Accordingly, do that. Back-patch as far as 9.0 so that the docs match the code in each branch.
* doc: Fix syntax of a URLPeter Eisentraut2013-01-20
| | | | | Leading white space before the "http:" is apparently treated as a relative link at least by some browsers.
* Clarify that streaming replication can be both async and syncMagnus Hagander2013-01-20
| | | | Josh Kupershmidt
* Update copyrights for 2013Bruce Momjian2013-01-01
| | | | | Fully update git head, and update back branches in ./COPYRIGHT and legal.sgml files.
* doc: Correct description of LDAP authenticationPeter Eisentraut2012-12-29
| | | | | | | Parts of the description had claimed incorrect pg_hba.conf option names for LDAP authentication. Albe Laurenz
* Fix pg_extension_config_dump() to handle update cases more sanely.Tom Lane2012-12-20
| | | | | | | | | | | | | | | | | | | | | | If pg_extension_config_dump() is executed again for a table already listed in the extension's extconfig, the code was blindly making a new array entry. This does not seem useful. Fix it to replace the existing array entry instead, so that it's possible for extension update scripts to alter the filter conditions for configuration tables. In addition, teach ALTER EXTENSION DROP TABLE to check for an extconfig entry for the target table, and remove it if present. This is not a 100% solution because it's allowed for an extension update script to just summarily DROP a member table, and that code path doesn't go through ExecAlterExtensionContentsStmt. We could probably make that case clean things up if we had to, but it would involve sticking a very ugly wart somewhere in the guts of dependency.c. Since on the whole it seems quite unlikely that extension updates would want to remove pre-existing configuration tables, making the case possible with an explicit command seems sufficient. Per bug #7756 from Regina Obe. Back-patch to 9.1 where extensions were introduced.
* Fix typoPeter Eisentraut2012-12-18
|
* Update iso.org page linkPeter Eisentraut2012-12-08
| | | | The old one is responding with 404.
* Update release notes for 9.2.2, 9.1.7, 9.0.11, 8.4.15, 8.3.22.Tom Lane2012-12-03
|
* Fix documentation of path(polygon) function.Tom Lane2012-12-03
| | | | | | | Obviously, this returns type "path", but somebody made a copy-and-pasteo long ago. Dagfinn Ilmari Mannsåker
* Recommend triggers, not rules, in the CREATE VIEW reference page.Tom Lane2012-12-02
| | | | | | We've generally recommended use of INSTEAD triggers over rules since that feature was added; but this old text in the CREATE VIEW reference page didn't get the memo. Noted by Thomas Kellerer.
* doc: Fix broken links to DocBook wikiPeter Eisentraut2012-12-01
|
* XSLT stylesheet: Add slash to directory namePeter Eisentraut2012-11-08
| | | | | | Some versions of the XSLT stylesheets don't handle the missing slash correctly (they concatenate directory and file name without the slash). This might never have worked correctly.
* Document that TCP keepalive settings read as 0 on Unix-socket connections.Tom Lane2012-10-31
| | | | | Per bug #7631 from Rob Johnson. The code is operating as designed, but the docs didn't explain it.
* Fix typo in previous commitSimon Riggs2012-10-17
|
* Clarify hash index caution and copy to CREATE INDEX docsSimon Riggs2012-10-17
|
* Removed sentence about not being able to retrieve more than one row at a time,Michael Meskes2012-10-05
| | | | because it is not correct.
* Fix permissions explanations in CREATE DATABASE and CREATE SCHEMA docs.Tom Lane2012-10-04
| | | | | | | | | | These reference pages still claimed that you have to be superuser to create a database or schema owned by a different role. That was true before 8.1, but it was changed in commits aa1110624c08298393dfce996f7b21809d98d3fd and f91370cd2faf1fd35a1ac74d84652a85ed841919 to allow assignment of ownership to any role you are a member of. However, at the time we were thinking of that primarily as a change to the ALTER OWNER rules, so the need to touch these two CREATE ref pages got missed.
* Fix tar files emitted by pg_basebackup to be POSIX conformant.Tom Lane2012-09-28
| | | | | | | | | | | | | Back-patch portions of commit 05b555d12bc2ad0d581f48a12b45174db41dc10d. There doesn't seem to be any reason not to fix pg_basebackup fully, but we can't change pg_dump's "magic" string without breaking older versions of pg_restore. Instead, just patch pg_restore to accept either version of the magic string, in hopes of avoiding compatibility problems when 9.3 comes out. I also fixed pg_dump to write the correct 2-block EOF marker, since that won't create a compatibility problem with pg_restore and it could help with some versions of tar. Brian Weaver and Tom Lane
* Fix examples of how to use "su" while starting the server.Tom Lane2012-09-25
| | | | | | | | The syntax "su -c 'command' username" is not accepted by all versions of su, for example not OpenBSD's. More portable is "su username -c 'command'". So change runtime.sgml to recommend that syntax. Also, add a -D switch to the OpenBSD example script, for consistency with other examples. Per Denis Lapshin and Gábor Hidvégi.
* Update release notes for 9.2.1, 9.1.6, 9.0.10, 8.4.14, 8.3.21.Tom Lane2012-09-19
|
* Provide adequate documentation of the "table_name *" notation.Tom Lane2012-09-17
| | | | | | | | | Somewhere along the line, somebody decided to remove all trace of this notation from the documentation text. It was still in the command syntax synopses, or at least some of them, but with no indication what it meant. This will not do, as evidenced by the confusion apparent in bug #7543; even if the notation is now unnecessary, people will find it in legacy SQL code and need to know what it does.
* Fix documentation reference to maximum allowed for autovacuum_freeze_max_age.Kevin Grittner2012-09-16
| | | | | | | | | The documentation mentioned setting autovacuum_freeze_max_age to "its maximum allowed value of a little less than two billion". This led to a post asking about the exact maximum allowed value, which is precisely two billion, not "a little less". Based on question by Radovan Jablonovsky. Backpatch to 8.3.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 21:21:30 +0000