2010-09-20 22:08:53 +02:00
|
|
|
<!-- doc/src/sgml/reference.sgml -->
|
1998-10-31 10:36:38 +01:00
|
|
|
|
2003-03-25 17:15:44 +01:00
|
|
|
<part id="reference">
|
|
|
|
<title>Reference</title>
|
2001-09-03 14:57:50 +02:00
|
|
|
|
2003-03-25 17:15:44 +01:00
|
|
|
<partintro>
|
2001-09-03 14:57:50 +02:00
|
|
|
<para>
|
2003-03-25 17:15:44 +01:00
|
|
|
The entries in this Reference are meant to provide in reasonable
|
|
|
|
length an authoritative, complete, and formal summary about their
|
|
|
|
respective subjects. More information about the use of
|
|
|
|
<productname>PostgreSQL</productname>, in narrative, tutorial, or
|
Update documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
Also update two error messages mentioned in the documenation to match.
2007-01-31 21:56:20 +01:00
|
|
|
example form, can be found in other parts of this book. See the
|
2003-03-25 17:15:44 +01:00
|
|
|
cross-references listed on each reference page.
|
2001-09-03 14:57:50 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2003-03-25 17:15:44 +01:00
|
|
|
The reference entries are also available as traditional
|
|
|
|
<quote>man</quote> pages.
|
2001-09-03 14:57:50 +02:00
|
|
|
</para>
|
2003-03-25 17:15:44 +01:00
|
|
|
</partintro>
|
2001-09-03 14:57:50 +02:00
|
|
|
|
2000-11-24 18:44:22 +01:00
|
|
|
<reference id="sql-commands">
|
|
|
|
<title>SQL Commands</title>
|
1998-05-13 07:34:39 +02:00
|
|
|
|
2000-11-24 18:44:22 +01:00
|
|
|
<partintro>
|
|
|
|
<para>
|
2001-09-03 14:57:50 +02:00
|
|
|
This part contains reference information for the
|
|
|
|
<acronym>SQL</acronym> commands supported by
|
|
|
|
<productname>PostgreSQL</productname>. By <quote>SQL</quote> the
|
|
|
|
language in general is meant; information about the standards
|
|
|
|
conformance and compatibility of each command can be found on the
|
|
|
|
respective reference page.
|
2000-11-24 18:44:22 +01:00
|
|
|
</para>
|
|
|
|
</partintro>
|
|
|
|
|
|
|
|
&abort;
|
2003-06-27 16:45:32 +02:00
|
|
|
&alterAggregate;
|
2011-02-12 14:54:13 +01:00
|
|
|
&alterCollation;
|
2003-06-27 16:45:32 +02:00
|
|
|
&alterConversion;
|
2002-03-01 23:45:19 +01:00
|
|
|
&alterDatabase;
|
2009-10-05 21:24:49 +02:00
|
|
|
&alterDefaultPrivileges;
|
2002-12-06 06:00:34 +01:00
|
|
|
&alterDomain;
|
2012-07-18 16:16:16 +02:00
|
|
|
&alterEventTrigger;
|
2013-11-15 14:44:18 +01:00
|
|
|
&alterExtension;
|
2008-12-19 17:25:19 +01:00
|
|
|
&alterForeignDataWrapper;
|
2011-01-02 05:48:11 +01:00
|
|
|
&alterForeignTable;
|
2003-06-27 16:45:32 +02:00
|
|
|
&alterFunction;
|
2000-11-24 18:44:22 +01:00
|
|
|
&alterGroup;
|
2004-08-21 18:16:04 +02:00
|
|
|
&alterIndex;
|
2003-06-27 16:45:32 +02:00
|
|
|
&alterLanguage;
|
2009-12-11 04:34:57 +01:00
|
|
|
&alterLargeObject;
|
2013-03-04 01:23:31 +01:00
|
|
|
&alterMaterializedView;
|
2004-06-25 23:55:59 +02:00
|
|
|
&alterOperator;
|
2003-06-27 16:45:32 +02:00
|
|
|
&alterOperatorClass;
|
2007-01-23 06:07:18 +01:00
|
|
|
&alterOperatorFamily;
|
Row-Level Security Policies (RLS)
Building on the updatable security-barrier views work, add the
ability to define policies on tables to limit the set of rows
which are returned from a query and which are allowed to be added
to a table. Expressions defined by the policy for filtering are
added to the security barrier quals of the query, while expressions
defined to check records being added to a table are added to the
with-check options of the query.
New top-level commands are CREATE/ALTER/DROP POLICY and are
controlled by the table owner. Row Security is able to be enabled
and disabled by the owner on a per-table basis using
ALTER TABLE .. ENABLE/DISABLE ROW SECURITY.
Per discussion, ROW SECURITY is disabled on tables by default and
must be enabled for policies on the table to be used. If no
policies exist on a table with ROW SECURITY enabled, a default-deny
policy is used and no records will be visible.
By default, row security is applied at all times except for the
table owner and the superuser. A new GUC, row_security, is added
which can be set to ON, OFF, or FORCE. When set to FORCE, row
security will be applied even for the table owner and superusers.
When set to OFF, row security will be disabled when allowed and an
error will be thrown if the user does not have rights to bypass row
security.
Per discussion, pg_dump sets row_security = OFF by default to ensure
that exports and backups will have all data in the table or will
error if there are insufficient privileges to bypass row security.
A new option has been added to pg_dump, --enable-row-security, to
ask pg_dump to export with row security enabled.
A new role capability, BYPASSRLS, which can only be set by the
superuser, is added to allow other users to be able to bypass row
security using row_security = OFF.
Many thanks to the various individuals who have helped with the
design, particularly Robert Haas for his feedback.
Authors include Craig Ringer, KaiGai Kohei, Adam Brightwell, Dean
Rasheed, with additional changes and rework by me.
Reviewers have included all of the above, Greg Smith,
Jeff McCormick, and Robert Haas.
2014-09-19 17:18:35 +02:00
|
|
|
&alterPolicy;
|
2005-07-27 01:24:02 +02:00
|
|
|
&alterRole;
|
2013-02-09 05:58:40 +01:00
|
|
|
&alterRule;
|
2003-06-27 16:45:32 +02:00
|
|
|
&alterSchema;
|
2003-03-20 08:02:11 +01:00
|
|
|
&alterSequence;
|
2008-12-19 17:25:19 +01:00
|
|
|
&alterServer;
|
2013-12-18 15:42:44 +01:00
|
|
|
&alterSystem;
|
2000-11-24 18:44:22 +01:00
|
|
|
&alterTable;
|
2004-06-25 23:55:59 +02:00
|
|
|
&alterTableSpace;
|
2007-08-21 23:08:47 +02:00
|
|
|
&alterTSConfig;
|
|
|
|
&alterTSDictionary;
|
|
|
|
&alterTSParser;
|
|
|
|
&alterTSTemplate;
|
2002-04-24 04:49:50 +02:00
|
|
|
&alterTrigger;
|
2004-06-25 23:55:59 +02:00
|
|
|
&alterType;
|
2000-11-24 18:44:22 +01:00
|
|
|
&alterUser;
|
2008-12-19 17:25:19 +01:00
|
|
|
&alterUserMapping;
|
2007-07-03 03:30:37 +02:00
|
|
|
&alterView;
|
2001-05-07 02:43:27 +02:00
|
|
|
&analyze;
|
2000-11-24 18:44:22 +01:00
|
|
|
&begin;
|
2001-01-13 04:11:12 +01:00
|
|
|
&checkpoint;
|
2000-11-24 18:44:22 +01:00
|
|
|
&close;
|
|
|
|
&cluster;
|
|
|
|
&commentOn;
|
|
|
|
&commit;
|
2005-06-18 00:32:51 +02:00
|
|
|
&commitPrepared;
|
2000-11-24 18:44:22 +01:00
|
|
|
©Table;
|
|
|
|
&createAggregate;
|
2002-07-19 01:11:32 +02:00
|
|
|
&createCast;
|
2011-02-12 14:54:13 +01:00
|
|
|
&createCollation;
|
2002-07-22 10:57:15 +02:00
|
|
|
&createConversion;
|
2000-11-24 18:44:22 +01:00
|
|
|
&createDatabase;
|
2002-03-19 03:18:25 +01:00
|
|
|
&createDomain;
|
2012-07-18 16:16:16 +02:00
|
|
|
&createEventTrigger;
|
2013-11-15 14:44:18 +01:00
|
|
|
&createExtension;
|
2008-12-19 17:25:19 +01:00
|
|
|
&createForeignDataWrapper;
|
2011-01-02 05:48:11 +01:00
|
|
|
&createForeignTable;
|
2000-11-24 18:44:22 +01:00
|
|
|
&createFunction;
|
|
|
|
&createGroup;
|
|
|
|
&createIndex;
|
|
|
|
&createLanguage;
|
2013-03-04 01:23:31 +01:00
|
|
|
&createMaterializedView;
|
2000-11-24 18:44:22 +01:00
|
|
|
&createOperator;
|
2002-07-30 00:14:11 +02:00
|
|
|
&createOperatorClass;
|
2007-01-23 06:07:18 +01:00
|
|
|
&createOperatorFamily;
|
Row-Level Security Policies (RLS)
Building on the updatable security-barrier views work, add the
ability to define policies on tables to limit the set of rows
which are returned from a query and which are allowed to be added
to a table. Expressions defined by the policy for filtering are
added to the security barrier quals of the query, while expressions
defined to check records being added to a table are added to the
with-check options of the query.
New top-level commands are CREATE/ALTER/DROP POLICY and are
controlled by the table owner. Row Security is able to be enabled
and disabled by the owner on a per-table basis using
ALTER TABLE .. ENABLE/DISABLE ROW SECURITY.
Per discussion, ROW SECURITY is disabled on tables by default and
must be enabled for policies on the table to be used. If no
policies exist on a table with ROW SECURITY enabled, a default-deny
policy is used and no records will be visible.
By default, row security is applied at all times except for the
table owner and the superuser. A new GUC, row_security, is added
which can be set to ON, OFF, or FORCE. When set to FORCE, row
security will be applied even for the table owner and superusers.
When set to OFF, row security will be disabled when allowed and an
error will be thrown if the user does not have rights to bypass row
security.
Per discussion, pg_dump sets row_security = OFF by default to ensure
that exports and backups will have all data in the table or will
error if there are insufficient privileges to bypass row security.
A new option has been added to pg_dump, --enable-row-security, to
ask pg_dump to export with row security enabled.
A new role capability, BYPASSRLS, which can only be set by the
superuser, is added to allow other users to be able to bypass row
security using row_security = OFF.
Many thanks to the various individuals who have helped with the
design, particularly Robert Haas for his feedback.
Authors include Craig Ringer, KaiGai Kohei, Adam Brightwell, Dean
Rasheed, with additional changes and rework by me.
Reviewers have included all of the above, Greg Smith,
Jeff McCormick, and Robert Haas.
2014-09-19 17:18:35 +02:00
|
|
|
&createPolicy;
|
2005-07-27 01:24:02 +02:00
|
|
|
&createRole;
|
2000-11-24 18:44:22 +01:00
|
|
|
&createRule;
|
2002-04-25 23:47:07 +02:00
|
|
|
&createSchema;
|
2000-11-24 18:44:22 +01:00
|
|
|
&createSequence;
|
2008-12-19 17:25:19 +01:00
|
|
|
&createServer;
|
2000-11-24 18:44:22 +01:00
|
|
|
&createTable;
|
|
|
|
&createTableAs;
|
2004-06-18 08:14:31 +02:00
|
|
|
&createTableSpace;
|
2007-08-21 23:08:47 +02:00
|
|
|
&createTSConfig;
|
|
|
|
&createTSDictionary;
|
|
|
|
&createTSParser;
|
|
|
|
&createTSTemplate;
|
2015-04-26 16:33:14 +02:00
|
|
|
&createTransform;
|
2000-11-24 18:44:22 +01:00
|
|
|
&createTrigger;
|
|
|
|
&createType;
|
|
|
|
&createUser;
|
2008-12-19 17:25:19 +01:00
|
|
|
&createUserMapping;
|
2000-11-24 18:44:22 +01:00
|
|
|
&createView;
|
2002-08-27 06:55:12 +02:00
|
|
|
&deallocate;
|
2000-11-24 18:44:22 +01:00
|
|
|
&declare;
|
|
|
|
&delete;
|
2007-04-26 18:13:15 +02:00
|
|
|
&discard;
|
2009-09-23 01:43:43 +02:00
|
|
|
&do;
|
2000-11-24 18:44:22 +01:00
|
|
|
&dropAggregate;
|
2002-07-19 01:11:32 +02:00
|
|
|
&dropCast;
|
2011-02-12 14:54:13 +01:00
|
|
|
&dropCollation;
|
2002-07-22 10:57:15 +02:00
|
|
|
&dropConversion;
|
2000-11-24 18:44:22 +01:00
|
|
|
&dropDatabase;
|
2002-03-19 03:18:25 +01:00
|
|
|
&dropDomain;
|
2012-07-18 16:16:16 +02:00
|
|
|
&dropEventTrigger;
|
2013-11-15 14:44:18 +01:00
|
|
|
&dropExtension;
|
2008-12-19 17:25:19 +01:00
|
|
|
&dropForeignDataWrapper;
|
2011-01-02 05:48:11 +01:00
|
|
|
&dropForeignTable;
|
2000-11-24 18:44:22 +01:00
|
|
|
&dropFunction;
|
|
|
|
&dropGroup;
|
|
|
|
&dropIndex;
|
|
|
|
&dropLanguage;
|
2013-03-04 01:23:31 +01:00
|
|
|
&dropMaterializedView;
|
2000-11-24 18:44:22 +01:00
|
|
|
&dropOperator;
|
2002-07-30 00:14:11 +02:00
|
|
|
&dropOperatorClass;
|
2007-01-23 06:07:18 +01:00
|
|
|
&dropOperatorFamily;
|
2005-11-21 13:49:33 +01:00
|
|
|
&dropOwned;
|
Row-Level Security Policies (RLS)
Building on the updatable security-barrier views work, add the
ability to define policies on tables to limit the set of rows
which are returned from a query and which are allowed to be added
to a table. Expressions defined by the policy for filtering are
added to the security barrier quals of the query, while expressions
defined to check records being added to a table are added to the
with-check options of the query.
New top-level commands are CREATE/ALTER/DROP POLICY and are
controlled by the table owner. Row Security is able to be enabled
and disabled by the owner on a per-table basis using
ALTER TABLE .. ENABLE/DISABLE ROW SECURITY.
Per discussion, ROW SECURITY is disabled on tables by default and
must be enabled for policies on the table to be used. If no
policies exist on a table with ROW SECURITY enabled, a default-deny
policy is used and no records will be visible.
By default, row security is applied at all times except for the
table owner and the superuser. A new GUC, row_security, is added
which can be set to ON, OFF, or FORCE. When set to FORCE, row
security will be applied even for the table owner and superusers.
When set to OFF, row security will be disabled when allowed and an
error will be thrown if the user does not have rights to bypass row
security.
Per discussion, pg_dump sets row_security = OFF by default to ensure
that exports and backups will have all data in the table or will
error if there are insufficient privileges to bypass row security.
A new option has been added to pg_dump, --enable-row-security, to
ask pg_dump to export with row security enabled.
A new role capability, BYPASSRLS, which can only be set by the
superuser, is added to allow other users to be able to bypass row
security using row_security = OFF.
Many thanks to the various individuals who have helped with the
design, particularly Robert Haas for his feedback.
Authors include Craig Ringer, KaiGai Kohei, Adam Brightwell, Dean
Rasheed, with additional changes and rework by me.
Reviewers have included all of the above, Greg Smith,
Jeff McCormick, and Robert Haas.
2014-09-19 17:18:35 +02:00
|
|
|
&dropPolicy;
|
2005-07-27 01:24:02 +02:00
|
|
|
&dropRole;
|
2000-11-24 18:44:22 +01:00
|
|
|
&dropRule;
|
2002-07-18 18:47:26 +02:00
|
|
|
&dropSchema;
|
2000-11-24 18:44:22 +01:00
|
|
|
&dropSequence;
|
2008-12-19 17:25:19 +01:00
|
|
|
&dropServer;
|
2000-11-24 18:44:22 +01:00
|
|
|
&dropTable;
|
2004-06-18 08:14:31 +02:00
|
|
|
&dropTableSpace;
|
2007-08-21 23:08:47 +02:00
|
|
|
&dropTSConfig;
|
|
|
|
&dropTSDictionary;
|
|
|
|
&dropTSParser;
|
|
|
|
&dropTSTemplate;
|
2015-04-26 16:33:14 +02:00
|
|
|
&dropTransform;
|
2000-11-24 18:44:22 +01:00
|
|
|
&dropTrigger;
|
2002-08-27 06:55:12 +02:00
|
|
|
&dropType;
|
2000-11-24 18:44:22 +01:00
|
|
|
&dropUser;
|
2008-12-19 17:25:19 +01:00
|
|
|
&dropUserMapping;
|
2000-11-24 18:44:22 +01:00
|
|
|
&dropView;
|
|
|
|
&end;
|
2002-08-27 06:55:12 +02:00
|
|
|
&execute;
|
2000-11-24 18:44:22 +01:00
|
|
|
&explain;
|
|
|
|
&fetch;
|
|
|
|
&grant;
|
2014-07-10 21:01:31 +02:00
|
|
|
&importForeignSchema;
|
2000-11-24 18:44:22 +01:00
|
|
|
&insert;
|
|
|
|
&listen;
|
|
|
|
&load;
|
|
|
|
&lock;
|
|
|
|
&move;
|
|
|
|
¬ify;
|
2002-08-27 06:55:12 +02:00
|
|
|
&prepare;
|
2005-06-18 00:32:51 +02:00
|
|
|
&prepareTransaction;
|
2005-11-21 13:49:33 +01:00
|
|
|
&reassignOwned;
|
2013-03-04 01:23:31 +01:00
|
|
|
&refreshMaterializedView;
|
2000-11-24 18:44:22 +01:00
|
|
|
&reindex;
|
2004-08-01 19:32:22 +02:00
|
|
|
&releaseSavepoint;
|
2000-11-24 18:44:22 +01:00
|
|
|
&reset;
|
|
|
|
&revoke;
|
|
|
|
&rollback;
|
2005-06-18 00:32:51 +02:00
|
|
|
&rollbackPrepared;
|
2004-08-01 19:32:22 +02:00
|
|
|
&rollbackTo;
|
|
|
|
&savepoint;
|
2010-09-28 02:55:27 +02:00
|
|
|
&securityLabel;
|
2000-11-24 18:44:22 +01:00
|
|
|
&select;
|
|
|
|
&selectInto;
|
|
|
|
&set;
|
|
|
|
&setConstraints;
|
2005-07-26 00:12:34 +02:00
|
|
|
&setRole;
|
2001-05-08 23:06:43 +02:00
|
|
|
&setSessionAuth;
|
2000-11-24 18:44:22 +01:00
|
|
|
&setTransaction;
|
|
|
|
&show;
|
2002-08-04 06:31:44 +02:00
|
|
|
&startTransaction;
|
2000-11-24 18:44:22 +01:00
|
|
|
&truncate;
|
|
|
|
&unlisten;
|
|
|
|
&update;
|
|
|
|
&vacuum;
|
2006-09-18 21:54:01 +02:00
|
|
|
&values;
|
2002-03-19 03:18:25 +01:00
|
|
|
|
2000-11-24 18:44:22 +01:00
|
|
|
</reference>
|
1998-05-13 07:34:39 +02:00
|
|
|
|
2000-11-24 18:44:22 +01:00
|
|
|
<reference id="reference-client">
|
2000-12-26 00:15:27 +01:00
|
|
|
<title>PostgreSQL Client Applications</title>
|
1998-05-13 07:34:39 +02:00
|
|
|
|
2000-11-24 18:44:22 +01:00
|
|
|
<partintro>
|
|
|
|
<para>
|
2001-09-03 14:57:50 +02:00
|
|
|
This part contains reference information for
|
|
|
|
<productname>PostgreSQL</productname> client applications and
|
2010-02-19 04:50:03 +01:00
|
|
|
utilities. Not all of these commands are of general utility; some
|
Update documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
Also update two error messages mentioned in the documenation to match.
2007-01-31 21:56:20 +01:00
|
|
|
might require special privileges. The common feature of these
|
2001-09-03 14:57:50 +02:00
|
|
|
applications is that they can be run on any host, independent of
|
|
|
|
where the database server resides.
|
2000-11-24 18:44:22 +01:00
|
|
|
</para>
|
2011-09-10 22:39:02 +02:00
|
|
|
|
|
|
|
<para>
|
2012-04-06 22:55:24 +02:00
|
|
|
When specified on the command line, user and database names have
|
2011-09-10 22:39:02 +02:00
|
|
|
their case preserved — the presence of spaces or special
|
|
|
|
characters might require quoting. Table names and other identifiers
|
|
|
|
do not have their case preserved, except where documented, and
|
|
|
|
might require quoting.
|
|
|
|
</para>
|
2000-11-24 18:44:22 +01:00
|
|
|
</partintro>
|
|
|
|
|
2002-08-27 05:38:28 +02:00
|
|
|
&clusterdb;
|
2000-11-24 18:44:22 +01:00
|
|
|
&createdb;
|
2001-09-03 14:57:50 +02:00
|
|
|
&createlang;
|
2000-11-24 18:44:22 +01:00
|
|
|
&createuser;
|
|
|
|
&dropdb;
|
2001-09-03 14:57:50 +02:00
|
|
|
&droplang;
|
2000-11-24 18:44:22 +01:00
|
|
|
&dropuser;
|
|
|
|
&ecpgRef;
|
2011-01-23 12:21:23 +01:00
|
|
|
&pgBasebackup;
|
2015-03-11 03:33:24 +01:00
|
|
|
&pgbench;
|
2000-11-24 18:44:22 +01:00
|
|
|
&pgConfig;
|
|
|
|
&pgDump;
|
|
|
|
&pgDumpall;
|
2013-01-23 16:58:04 +01:00
|
|
|
&pgIsready;
|
2011-10-26 20:13:33 +02:00
|
|
|
&pgReceivexlog;
|
2014-03-18 18:20:01 +01:00
|
|
|
&pgRecvlogical;
|
2000-11-24 18:44:22 +01:00
|
|
|
&pgRestore;
|
2003-03-24 15:32:51 +01:00
|
|
|
&psqlRef;
|
2005-07-29 17:13:11 +02:00
|
|
|
&reindexdb;
|
2000-11-24 18:44:22 +01:00
|
|
|
&vacuumdb;
|
|
|
|
|
|
|
|
</reference>
|
|
|
|
|
|
|
|
<reference id="reference-server">
|
2000-12-26 00:15:27 +01:00
|
|
|
<title>PostgreSQL Server Applications</title>
|
2000-11-24 18:44:22 +01:00
|
|
|
|
|
|
|
<partintro>
|
|
|
|
<para>
|
2001-09-03 14:57:50 +02:00
|
|
|
This part contains reference information for
|
|
|
|
<productname>PostgreSQL</productname> server applications and
|
|
|
|
support utilities. These commands can only be run usefully on the
|
|
|
|
host where the database server resides. Other utility programs
|
|
|
|
are listed in <xref linkend="reference-client">.
|
2000-11-24 18:44:22 +01:00
|
|
|
</para>
|
|
|
|
</partintro>
|
|
|
|
|
|
|
|
&initdb;
|
2015-03-11 03:33:23 +01:00
|
|
|
&pgarchivecleanup;
|
2002-08-16 22:34:06 +02:00
|
|
|
&pgControldata;
|
2003-03-24 15:32:51 +01:00
|
|
|
&pgCtl;
|
2002-08-17 05:38:43 +02:00
|
|
|
&pgResetxlog;
|
2015-03-23 18:47:52 +01:00
|
|
|
&pgRewind;
|
2015-03-11 03:33:24 +01:00
|
|
|
&pgtestfsync;
|
2015-03-11 03:33:24 +01:00
|
|
|
&pgtesttiming;
|
2015-03-11 03:33:25 +01:00
|
|
|
&pgupgrade;
|
2015-03-11 03:33:24 +01:00
|
|
|
&pgxlogdump;
|
2000-11-24 18:44:22 +01:00
|
|
|
&postgres;
|
|
|
|
&postmaster;
|
|
|
|
|
|
|
|
</reference>
|
1998-05-13 07:34:39 +02:00
|
|
|
|
2003-03-25 17:15:44 +01:00
|
|
|
</part>
|