aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref
Commit message (Collapse)AuthorAge
* doc: small fixes for REINDEX reference pagePeter Eisentraut2014-07-14
| | | | From: Josh Kupershmidt <schmiddy@gmail.com>
* 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.
* Fix typos in pg_basebackup documentationMagnus Hagander2014-03-25
| | | | Joshua Tolley
* 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
* 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.
* 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.
* Remove stray | characterMagnus Hagander2013-07-05
| | | | Erikjan Rijkers
* 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
* 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.
* 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.
* 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.
* 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.
* Make pg_dump exclude unlogged table data on hot standby slavesMagnus Hagander2013-01-25
| | | | Noted by Joe Van Dyk
* Fix typoPeter Eisentraut2012-12-18
|
* 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.
* Fix typo in previous commitSimon Riggs2012-10-17
|
* Clarify hash index caution and copy to CREATE INDEX docsSimon Riggs2012-10-17
|
* 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.
* 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.
* Reword documentation for concurrent index rebuilds to be clearer.Bruce Momjian2012-08-04
| | | | Backpatch to 9.1 and 9.2.
* Document that, for psql -c, only the result of the last command isBruce Momjian2012-08-03
| | | | | | returned, per report from Aleksey Tsalolikhin Backpatch to 9.2 and 9.1.
* Remove tabs in SGML filesBruce Momjian2012-03-12
|
* Add description for --no-locale and --text-search-config.Tatsuo Ishii2012-03-11
|
* Require execute permission on the trigger function for CREATE TRIGGER.Tom Lane2012-02-23
| | | | | | | | | | | | | | | | | This check was overlooked when we added function execute permissions to the system years ago. For an ordinary trigger function it's not a big deal, since trigger functions execute with the permissions of the table owner, so they couldn't do anything the user issuing the CREATE TRIGGER couldn't have done anyway. However, if a trigger function is SECURITY DEFINER, that is not the case. The lack of checking would allow another user to install it on his own table and then invoke it with, essentially, forged input data; which the trigger function is unlikely to realize, so it might do something undesirable, for instance insert false entries in an audit log table. Reported by Dinesh Kumar, patch by Robert Haas Security: CVE-2012-0866
* Update statement about sorting of character-string data.Tom Lane2012-01-28
| | | | | The sort order is no longer fixed at database creation time, but can be controlled via COLLATE. Noted by Thomas Kellerer.
* Clarify documentation about SQL:2008 variant of LIMIT/OFFSET syntax.Tom Lane2011-12-01
| | | | | The point that you need parentheses for non-constant expressions apparently needs to be brought out a bit more clearly, per bug #6315.
* Clarify that ORDER BY/FOR UPDATE can't malfunction at higher iso levels.Robert Haas2011-10-28
| | | | Kevin Grittner
* Fix typoMagnus Hagander2011-10-25
|
* Improve documentation of psql's \q command.Tom Lane2011-10-12
| | | | | | The documentation neglected to explain its behavior in a script file (it only ends execution of the script, not psql as a whole), and failed to mention the long form \quit either.
* Spelling improvementPeter Eisentraut2011-08-27
|
* Adjust CREATE DOMAIN example for standard_conforming_strings=on.Robert Haas2011-08-25
| | | | Noted by Hitoshi Harada.
* Adjust wording now that estimated size can increaseMagnus Hagander2011-08-17
| | | | Per comment form Fujii Masao.
* Add "Compatibility" section to ALTER EXTENSION reference pagePeter Eisentraut2011-08-07
| | | | Almost all other pages have one; this one must have been forgotten.
* Remove whitespace from end of linesPeter Eisentraut2011-08-07
|
* Fix a whitespace issue with the man pagesPeter Eisentraut2011-08-07
| | | | | | | | | | | | | | | | | | | | | There is what may actually be a mistake in our markup. The problem is in a situation like <para> <command>FOO</command> is ... there is strictly speaking a line break before "FOO". In the HTML output, this does not appear to be a problem, but in the man page output, this shows up, so you get double blank lines at odd places. So far, we have attempted to work around this with an XSL hack, but that causes other problems, such as creating run-ins in places like <acronym>SQL</acronym> <command>COPY</command> So fix the problem properly by removing the extra whitespace. I only fixed the problems that affect the man page output, not all the places.
* Fix typo.Robert Haas2011-07-27
| | | | Noted by Josh Kupershmidt.
* Clarify which relkinds accept column comments.Robert Haas2011-07-26
| | | | Per discussion with Josh Kupershmidt.
* Change EDITOR_LINENUMBER_SWITCH to an environment variablePeter Eisentraut2011-07-24
| | | | | | | | | | | Also change "switch" to "arg" because "switch" is a bit of a sloppy term. So the environment variable is called PSQL_EDITOR_LINENUMBER_ARG. Set "+" as hardcoded default value on Unix (since "vi" is the hardcoded default editor), so many users won't have to configure this at all. Move the documentation around a bit to centralize the editor configuration under environment variables, rather than repeating bits of it under every backslash command that invokes an editor.
* Improve sepgsql and SECURITY LABEL documentation.Robert Haas2011-07-20
| | | | | KaiGai Kohei, based on feedback from Yeb Havinga, with some corrections by me.
* Unify spelling of "canceled", "canceling", "cancellation"Peter Eisentraut2011-07-02
| | | | | We had previously (af26857a2775e7ceb0916155e931008c2116632f) established the U.S. spellings as standard.
* Fix typo.Robert Haas2011-06-17
| | | | Per Josh Kupershmidt and Tom Lane.
* Rework parsing of ConstraintAttributeSpec to improve NOT VALID handling.Tom Lane2011-06-15
| | | | | | | | | | | The initial commit of the ALTER TABLE ADD FOREIGN KEY NOT VALID feature failed to support labeling such constraints as deferrable. The best fix for this seems to be to fold NOT VALID into ConstraintAttributeSpec. That's a bit more general than the documented syntax, but it allows better-targeted syntax error messages. In addition, do some mostly-but-not-entirely-cosmetic code review for the whole NOT VALID patch.
* Document that psql's \d also works with composite typesPeter Eisentraut2011-06-14
| | | | This has always been true, it was just never documented.
* Improve accuracy of ON_ERROR_STOP documentation.Robert Haas2011-06-14
| | | | Per a gripe from Tom Lane.
* Expand warnings on locks acquired by CREATE INDEX CONCURRENTLYAlvaro Herrera2011-06-13
| | | | | | | | | The previous wording wasn't explicit enough, which could misled readers into thinking that the locks acquired are more restricted in nature than they really are. The resulting optimism can be damaging to morale when confronted with reality, as has been observed in the field. Greg Smith
* In ALTER EXTENSION docs, document left_type/right_type.Robert Haas2011-06-13
| | | | Noted by Daniele Varrazzo.
* Corrections to ALTER FOREIGN TABLE documentation.Robert Haas2011-06-12
| | | | Shigeru Hanada, with a minor grammar correction.
* Support silent mode for service registrations on win32Magnus Hagander2011-06-09
| | | | | | | | Using -s when registering a service will now suppress the application eventlog entries stating that the service is starting and started. MauMau
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-07 21:33:33 +0000