summaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref
AgeCommit message (Collapse)Author
2012-05-08psql: Add variable to control keyword case in tab completionPeter Eisentraut
This adds the variable COMP_KEYWORD_CASE, which controls in what case keywords are completed. This is partially to let users configure the change from commit 69f4f1c3576abc535871c6cfa95539e32a36120f, but it also offers more behaviors than were available before.
2012-05-06Document that it is the pgsql version we are matching for psqlrcBruce Momjian
version-specific files, not the server version.
2012-05-06Revert typo fix 768c3affd44d1dcb4e43e2e006c642524714c2a4; I was wrong.Bruce Momjian
2012-05-05Fix psql doc typo.Bruce Momjian
2012-05-03doc: Fix for too many brackets in command synopses on man pagesPeter Eisentraut
The default for the choice attribute of the <arg> element is "opt", which would normally put the argument inside brackets. But the DSSSL stylesheets contain a hack that treats <arg> directly inside <group> specially, so that <group><arg>-x</arg><arg>-y</arg></group> comes out as [ -x | -y ] rather than [ [-x] | [-y] ], which it would technically be. But when building man pages, this doesn't work, and so the command synopses on the man pages contain lots of extra brackets. By putting choice="opt" or choice="plain" explicitly on every <arg> and <group> element, we avoid any toolchain dependencies like that, and it also makes it clearer in the source code what is meant. In passing, make some small corrections in the documentation about which arguments are really optional or not.
2012-04-30Improve markup of cmdsynopsis elementsPeter Eisentraut
Add more markup in particular so that the command options appear consistently in monospace in the HTML output. On the vacuumdb reference page, remove listing all the possible options in the synopsis. They have become too many now; we have the detailed options list for that.
2012-04-24Casts to or from a domain type are ignored; warn and document.Robert Haas
Prohibiting this outright would break dumps taken from older versions that contain such casts, which would create far more pain than is justified here. Per report by Jaime Casanova and subsequent discussion.
2012-04-23Minor improvements for CHECK NO INHERIT documentation.Robert Haas
Fix typo spotted by Thom Brown, and improve wording in another area where Thom spotted a typo.
2012-04-20Recast "ONLY" column CHECK constraints as NO INHERITAlvaro Herrera
The original syntax wasn't universally loved, and it didn't allow its usage in CREATE TABLE, only ALTER TABLE. It now works everywhere, and it also allows using ALTER TABLE ONLY to add an uninherited CHECK constraint, per discussion. The pg_constraint column has accordingly been renamed connoinherit. This commit partly reverts some of the changes in 61d81bd28dbec65a6b144e0cd3d0bfe25913c3ac, particularly some pg_dump and psql bits, because now pg_get_constraintdef includes the necessary NO INHERIT within the constraint definition. Author: Nikhil Sontakke Some tweaks by me
2012-04-16Add compatibility information for prepared transaction commandsPeter Eisentraut
2012-04-14Add description of long options for '-c', '-D', '-l' and '-s'. PerTatsuo Ishii
discussion of hackers list on 2012/3/10 "missing description initdb manual".
2012-04-14Document that VALUES can be used in WITHPeter Eisentraut
2012-04-11Accept postgres:// URIs in libpq connection functionsAlvaro Herrera
postgres:// URIs are an attempt to "stop the bleeding" in this general area that has been said to occur due to external projects adopting their own syntaxes. The syntaxes supported by this patch: postgres://[user[:pwd]@][unix-socket][:port[/dbname]][?param1=value1&...] postgres://[user[:pwd]@][net-location][:port][/dbname][?param1=value1&...] should be enough to cover most interesting cases without having to resort to "param=value" pairs, but those are provided for the cases that need them regardless. libpq documentation has been shuffled around a bit, to avoid stuffing all the format details into the PQconnectdbParams description, which was already a bit overwhelming. The list of keywords has moved to its own subsection, and the details on the URI format live in another subsection. This includes a simple test program, as requested in discussion, to ensure that interesting corner cases continue to work appropriately in the future. Author: Alexander Shulgin Some tweaking by Álvaro Herrera, Greg Smith, Daniel Farina, Peter Eisentraut Reviewed by Robert Haas, Alexey Klyukin (offlist), Heikki Linnakangas, Marko Kreen, and others Oh, it also supports postgresql:// but that's probably just an accident.
2012-04-06Fix some typos in the documentationPeter Eisentraut
Thom Brown
2012-04-06Allow statistics to be collected for foreign tables.Tom Lane
ANALYZE now accepts foreign tables and allows the table's FDW to control how the sample rows are collected. (But only manual ANALYZEs will touch foreign tables, for the moment, since among other things it's not very clear how to handle remote permissions checks in an auto-analyze.) contrib/file_fdw is extended to support this. Etsuro Fujita, reviewed by Shigeru Hanada, some further tweaking by me.
2012-04-06Add DROP INDEX CONCURRENTLY [IF EXISTS], uses ShareUpdateExclusiveLockSimon Riggs
2012-04-03Add support for renaming domain constraintsPeter Eisentraut
2012-03-28Tweak markup to avoid extra whitespace in man pagesPeter Eisentraut
2012-03-22If a role has a password expiration date, show that in psql's \du output.Tom Lane
Per a suggestion from Euler Taveira, it seems like a good idea to include this information in \du (and \dg) output. This costs nothing for people who are not using the VALID UNTIL feature, while for those who are, it's rather critical information. Fabrízio de Royes Mello
2012-03-17Add note about column privilege behavior to REVOKE reference pagePeter Eisentraut
suggested by Josh Berkus
2012-03-12Remove tabs in SGML filesBruce Momjian
2012-03-11Make parameter name consistent with syntax summary.Tom Lane
Thomas Hunger
2012-03-11Add description for --no-locale and --text-search-config.Tatsuo Ishii
2012-03-10Add support for renaming constraintsPeter Eisentraut
reviewed by Josh Berkus and Dimitri Fontaine
2012-03-03Provide environment overrides for psql file locations.Andrew Dunstan
PSQL_HISTORY provides an alternative for the command history file, and PSQLRC provides an alternative location for the .psqlrc file.
2012-03-03Allow CREATE TABLE (LIKE ...) from composite typePeter Eisentraut
The only reason this didn't work before was that parserOpenTable() rejects composite types. So use relation_openrv() directly and manually do the errposition() setup that parserOpenTable() does.
2012-03-01Small possible clarification in pg_basebackup reference pagePeter Eisentraut
The <literal> markup is not visible as distinct on man pages, which creates a bit of confusion when looking at the documentation of the pg_basebackup -l option. Rather than reinventing the entire font system for man pages to remedy this, just put some quotes around this particular case, which should also help in other output formats.
2012-02-23Require execute permission on the trigger function for CREATE TRIGGER.Tom Lane
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
2012-02-22Make EXPLAIN (BUFFERS) track blocks dirtied, as well as those written.Robert Haas
Also expose the new counters through pg_stat_statements. Patch by me. Review by Fujii Masao and Greg Smith.
2012-02-15Make CREATE/ALTER FUNCTION support NOT LEAKPROOF.Robert Haas
Because it isn't good to be able to turn things on, and not off again.
2012-02-13Allow LEAKPROOF functions for better performance of security views.Robert Haas
We don't normally allow quals to be pushed down into a view created with the security_barrier option, but functions without side effects are an exception: they're OK. This allows much better performance in common cases, such as when using an equality operator (that might even be indexable). There is an outstanding issue here with the CREATE FUNCTION / ALTER FUNCTION syntax: there's no way to use ALTER FUNCTION to unset the leakproof flag. But I'm committing this as-is so that it doesn't have to be rebased again; we can fix up the grammar in a future commit. KaiGai Kohei, with some wordsmithing by me.
2012-02-09psql: Support zero byte field and record separatorsPeter Eisentraut
Add new psql settings and command-line options to support setting the field and record separators for unaligned output to a zero byte, for easier interfacing with other shell tools. reviewed by Abhijit Menon-Sen
2012-02-07Add TIMING option to EXPLAIN, to allow eliminating of timing overhead.Robert Haas
Sometimes it may be useful to get actual row counts out of EXPLAIN (ANALYZE) without paying the cost of timing every node entry/exit. With this patch, you can say EXPLAIN (ANALYZE, TIMING OFF) to get that. Tomas Vondra, reviewed by Eric Theise, with minor doc changes by me.
2012-02-07createuser: Disable prompting by defaultPeter Eisentraut
Do not prompt when options were not specified. Assume --no-createdb, --no-createrole, --no-superuser by default. Also disable prompting for user name in dropdb, unless --interactive was specified. reviewed by Josh Kupershmidt
2012-02-01initdb: Add options --auth-local and --auth-hostPeter Eisentraut
reviewed by Robert Haas and Pavel Stehule
2012-01-30Add sequence USAGE privileges to information schemaPeter Eisentraut
The sequence USAGE privilege is sufficiently similar to the SQL standard that it seems reasonable to show in the information schema. Also add some compatibility notes about it on the GRANT reference page.
2012-01-28Update statement about sorting of character-string data.Tom Lane
The sort order is no longer fixed at database creation time, but can be controlled via COLLATE. Noted by Thomas Kellerer.
2012-01-27Document that analyzing an empty table doesn't update the statistics.Robert Haas
Per a suggestion from Sergey Konoplev
2012-01-27Fix copy-paste error in docs.Heikki Linnakangas
Dean Rasheed
2012-01-25Allow pg_basebackup from standby node with safety checking.Simon Riggs
Base backup follows recommended procedure, plus goes to great lengths to ensure that partial page writes are avoided. Jun Ishizuka and Fujii Masao, with minor modifications
2012-01-23ALTER <thing> [IF EXISTS] ... allows silent DDL if required,Simon Riggs
e.g. ALTER FOREIGN TABLE IF EXISTS foo RENAME TO bar Pavel Stehule
2012-01-16Disallow merging ONLY constraints in children tablesAlvaro Herrera
When creating a child table, or when attaching an existing table as child of another, we must not allow inheritable constraints to be merged with non-inheritable ones, because then grandchildren would not properly get the constraint. This would violate the grandparent's expectations. Bugs noted by Robert Haas. Author: Nikhil Sontakke
2012-01-14Make superuser imply replication privilege. The idea of a privilege thatHeikki Linnakangas
superuser doesn't have doesn't make much sense, as a superuser can do whatever he wants through other means, anyway. So instead of granting replication privilege to superusers in CREATE USER time by default, allow replication connection from superusers whether or not they have the replication privilege. Patch by Noah Misch, per discussion on bug report #6264
2012-01-10Support CREATE TABLE (LIKE ...) with foreign tables and viewsPeter Eisentraut
Composite types are not yet supported, because parserOpenTable() rejects them.
2012-01-09Add compatibility note about grant options on GRANT reference pagePeter Eisentraut
Point out in the compatibility section that granting grant options to PUBLIC is not supported by PostgreSQL. This is already mentioned earlier, but since it concerns the information schema, it might be worth pointing out explicitly as a compatibility issue.
2012-01-07Rename the internal structures of the CREATE TABLE (LIKE ...) facilityPeter Eisentraut
The original implementation of this interpreted it as a kind of "inheritance" facility and named all the internal structures accordingly. This turned out to be very confusing, because it has nothing to do with the INHERITS feature. So rename all the internal parser infrastructure, update the comments, adjust the error messages, and split up the regression tests.
2012-01-05Improve ALTER DOMAIN / DROP CONSTRAINT with nonexistent constraintPeter Eisentraut
ALTER DOMAIN / DROP CONSTRAINT on a nonexistent constraint name did not report any error. Now it reports an error. The IF EXISTS option was added to get the usual behavior of ignoring nonexistent objects to drop.
2011-12-22Typo fixes.Robert Haas
All noted by Jaime Casanova.
2011-12-22Add a security_barrier option for views.Robert Haas
When a view is marked as a security barrier, it will not be pulled up into the containing query, and no quals will be pushed down into it, so that no function or operator chosen by the user can be applied to rows not exposed by the view. Views not configured with this option cannot provide robust row-level security, but will perform far better. Patch by KaiGai Kohei; original problem report by Heikki Linnakangas (in October 2009!). Review (in earlier versions) by Noah Misch and others. Design advice by Tom Lane and myself. Further review and cleanup by me.
2011-12-22Add ALTER DOMAIN ... RENAMEPeter Eisentraut
You could already rename domains using ALTER TYPE, but with this new command it is more consistent with how other commands treat domains as a subcategory of types.
generated by cgit v1.2.3 (git 2.46.0) at 2025-11-22 02:45:36 +0000