This option emits log lines in comma-separated-values
with these columns:
- timestamp with milliseconds,
+ time stamp with milliseconds,
user name,
database name,
process ID,
Sets the collection of time zone abbreviations that will be accepted
by the server for datetime input. The default is 'Default',
which is a collection that works in most of the world; there are
- also 'Australia' and 'India', and other collections can be defined
+ also 'Australia' and 'India', and other collections can be defined
for a particular installation. See
linkend="datetime-appendix"> for more information.
be present in the table. It is useful for recovering data if
corruption has occurred due to a hardware or software error. You should
generally not set this on until you have given up hope of recovering
- data from the damaged pages of a table. Zerod-out pages are not
+ data from the damaged pages of a table. Zeroed-out pages are not
forced to disk so it is recommended to recreate the table or
the index before turning this parameter off again. The
default setting is off, and it can only be changed
- Also, a configuration parameter can be retreived with the
+ Also, a configuration parameter can be retrieved with the
SHOW command:
EXEC SQL SHOW search_path INTO :var;
the pgtypes library. The pgtypes library, described in detail
in contains basic functions to deal
with those types, such that you do not need to send a query to
- the SQL server just for adding an interval to a timestamp for
+ the SQL server just for adding an interval to a time stamp for
example.
In addition, the DATE type can be handled in the same way. The
- program has to include pg_types_date.h, declare a host variable
+ program has to include pg_types_date.h, declare a host variable
as the date type and convert a DATE value into a text form using
- PGTYPESdate_to_asc() function. For more details about the
+ PGTYPESdate_to_asc() function. For more details about the
pgtypes library functions, see .
is a way to store some text string in char[]
or VARCHAR[], as
explained . The second use case is to
- retreive multiple rows from a query result without using a
+ retrieve multiple rows from a query result without using a
cursor. Without an array, to process a query result consisting
of multiple rows, it is required to use a cursor and
the FETCH command. But with array host
variables, multiple rows can be received at once. The length of
- the array has to be defined to be able to accomodate all rows,
+ the array has to be defined to be able to accommodate all rows,
otherwise a buffer overflow will likely occur.
The following example retrieves OIDs, names, and sizes of the
- avilable databases from the pg_database
+ available databases from the pg_database
system table and using
the pg_database_size() function. In this
example, a structure variable dbinfo_t with
%p - is replaced by national representation of
- either "ante meridiem" or "post meridiem" as appropriate.
+ either ante meridiem
or post meridiem
as appropriate.
-
SQLDA Data<span class="marked">c</span> Structure
+
SQLDA Data Structure
SQLDA uses three data structure
-
Retr<span class="marked">ei</span>ving a Result Set Using an SQLDA
+
Retr<span class="marked">ie</span>ving a Result Set Using an SQLDA
This application joins two system tables, pg_database and
- pg_stat_database on the database oid, and also fetches and shows
- the database statistics which are retreived by two input
- parameters (a database "postgres", and oid "1").
+ pg_stat_database on the database OID, and also fetches and shows
+ the database statistics which are retrieved by two input
+ parameters (a database postgres, and OID 1).
Large object functions have to be called in a transaction block, so
when autocommit is off, BEGIN commands have to
- be isssued explicitly.
+ be issued explicitly.
prepared_name
- The name of a prepared query, either as an SQL identfier or a
+ The name of a prepared query, either as an SQL identifier or a
host variable.
descriptor_item
- A token identifiying which item of information to set in the
+ A token identifying which item of information to set in the
descriptor. See for a
list of supported items.
right to -1 indicates that all available decimal digits
should be included in the output. If the length of the output buffer,
which is indicated by len is not sufficient to hold the
- textual representation including the trailing NUL character, only a
+ textual representation including the trailing zero byte, only a
single * character is stored in the result and -1 is
returned.
The function receives two arguments, the first one is the date to
convert (d and the second one is a pointer to the target
string. The output format is always yyyy-mm-dd, so you need
- to allocate at least 11 bytes (including the NUL-terminator) for the
+ to allocate at least 11 bytes (including the zero-byte terminator) for the
string.
A useful extension to
PostgreSQL typically includes- multiple SQL objects; for example, a new datatype will require new
+ multiple SQL objects; for example, a new data type will require new
functions, new operators, and probably new index operator classes.
It is helpful to collect all these objects into a single package
to simplify database management.
PostgreSQL calls
The file_fdw module provides the foreign-data wrapper
file_fdw, which can be used to access data
- files in the server's filesystem. Data files must be in a format
+ files in the server's file system. Data files must be in a format
that can be read by COPY FROM;
see for details.
-
<span class="marked">IS DOCUMENT</span>
+
<span class="marked"><literal>IS DOCUMENT</literal></span>
-
<span class="marked">XMLEXISTS</span>
+
<span class="marked"><literal>XMLEXISTS</literal></span>
-
<span class="marked">xml_is_well_formed</span>
+
<span class="marked"><literal>xml_is_well_formed</literal></span>
These functions check whether a text string is well-formed XML,
- returning a boolean result.
+ returning a Boolean result.
xml_is_well_formed_document checks for a well-formed
document, while xml_is_well_formed_content checks
for well-formed content. xml_is_well_formed does
The function xpath_exists is a specialized form
of the xpath function. Instead of returning the
individual XML values that satisfy the XPath, this function returns a
- boolean indicating whether the query was satisfied or not. This
+ Boolean indicating whether the query was satisfied or not. This
function is equivalent to the standard XMLEXISTS predicate,
except that it also offers support for a namespace mapping argument.
|
txid_snapshot_xmax(txid_snapshot)
bigint
- get xmax of snapshot
+ get xmax of snapshot
|
txid_snapshot_xmin(txid_snapshot)
bigint
- get xmin of snapshot
+ get xmin of snapshot
|
txid_visible_in_snapshot(bigint, txid_snapshot)
pg_last_xact_replay_timestamp()
timestamp with time zone
- Get timestamp of last transaction replayed during recovery.
+ Get time stamp of last transaction replayed during recovery.
This is the time at which the commit or abort WAL record for that
transaction was generated on the primary.
If no transactions have been replayed during recovery, this function
pg_read_binary_file is similar to
- pg_read_file, except that the result is a bytea value;
+ pg_read_file, except that the result is a bytea value;
accordingly, no encoding checks are performed.
In combination with the convert_from function, this function
can be used to read a file in a specified encoding:
To trigger failover of a log-shipping standby server,
run pg_ctl promote or create a trigger
- file with the filename and path specified by the trigger_file
+ file with the file name and path specified by the trigger_file
setting in recovery.conf. If you're planning to use
pg_ctl promote to fail over, trigger_file is
not required. If you're setting up the reporting servers that are
PostgreSQL works on AIX, but getting it installed properly can be
challenging. AIX versions from 4.3.3 to 6.1 are considered supported.
- You can use GCC or the native IBM compiler xlc. In
+ You can use GCC or the native IBM compiler xlc. In
general, using recent versions of AIX and PostgreSQL helps. Check
the build farm for up to date information about which versions of
AIX are known to work.
You can build with either GCC or Sun's compiler suite. For
better code optimization, Sun's compiler is strongly recommended
on the SPARC architecture. We have heard reports of problems
- when using GCC 2.95.1; gcc 2.95.3 or later is recommended. If
+ when using GCC 2.95.1; GCC 2.95.3 or later is recommended. If
you are using Sun's compiler, be careful not to select
/usr/ucb/cc;
use /opt/SUNWspro/bin/cc.
parameter can be used to achieve the kind of server
authentication that SSL certificates achieve on TCP/IP
connections. (Note that if the Unix-domain socket is
- in /tmp or another publically writable
+ in /tmp or another publicly writable
location, any user could start a server there. Use this
parameter to ensure that you are connected to a server run
by a trusted user,
The result of this function can be used to determine, at
- runtime, if specific functionality is available in the currently
+ run time, if specific functionality is available in the currently
loaded version of libpq. The function can be used, for example,
to determine which connection options are available for
PQconnectdb or if the hex bytea
pg_stat_activitypg_stat_activity
One row per server process, showing database OID, database
name, process
ID, user OID, user name, application name,- client's address, hostname (if available), and port number, times at
+ client's address, host name (if available), and port number, times at
which the server process, current transaction, and current query began
execution, process's waiting status, and text of the current query.
The columns that report data on the current query are available unless
the parameter track_activities has been turned off.
Furthermore, these columns are only visible if the user examining
the view is a superuser or the same as the user owning the process
- being reported on. The client's hostname will be available only if
- is set or if the user's hostname
+ being reported on. The client's host name will be available only if
+ is set or if the user's host name
needed to be looked up during pg_hba.conf
processing.
|
pg_stat_replicationpg_stat_replication
One row per WAL sender process, showing process ID,
- user OID, user name, application name, client's address, hostname
+ user OID, user name, application name, client's address, host name
(if available) and port number, time at which the server process began
execution, and the current WAL sender state and transaction log
location. In addition, the standby reports the last transaction log
is shown here also, that is the order in which standbys will become
the synchronous standby. The columns detailing what exactly the connection
is doing are only visible if the user examining the view is a superuser.
- The client's hostname will be available only if
- is set or if the user's hostname
+ The client's host name will be available only if
+ is set or if the user's host name
needed to be looked up during pg_hba.conf
processing.
with a SQLSTATE value of '40001'), because it will be very hard to
predict exactly which transactions might contribute to the read/write
dependencies and need to be rolled back to prevent serialization
- anomalies. The monitoring of read/write dependences has a cost, as does
+ anomalies. The monitoring of read/write dependencies has a cost, as does
the restart of transactions which are terminated with a serialization
failure, but balanced against the cost and blocking involved in use of
explicit locks and SELECT FOR UPDATE or SELECT FOR
the related Insert, Update, or Delete node, although time spent executing
AFTER triggers is not. The time spent in each trigger
(either BEFORE or AFTER) is also shown separately
- and is included in total runtime.
+ and is included in total run time.
Note, however, that deferred constraint triggers will not be executed
until end of transaction and are thus not shown by
EXPLAIN ANALYZE.
- There are two significant ways in which runtimes measured by
+ There are two significant ways in which run times measured by
EXPLAIN ANALYZE can deviate from normal execution of
the same query. First, since no output rows are delivered to the client,
network transmission costs and I/O formatting costs are not included.
- Specifies the filename to write test data in.
+ Specifies the file name to write test data in.
This file should be in the same file system that the
pg_xlog directory is or will be placed in.
(
pg_xlog contains the WAL files.)
Arguments will be converted from the database's encoding to UTF-8
- for use inside plperl, and then converted from UTF-8 back to the
+ for use inside PL/Perl, and then converted from UTF-8 back to the
database encoding upon return.
encode_typed_literal(value, typename)
- Converts a Perl variable to the value of the datatype passed as a
+ Converts a Perl variable to the value of the data type passed as a
second argument and returns a string representation of this value.
Correctly handles nested arrays and values of composite types.
child processes.
- This parameter can only be set in the postgresql.conf file or on the server command line.
+ This parameter can only be set in the postgresql.conf file or on the server command line.
This example uses a trigger on the view to make it updatable, and
ensure that any insert, update or delete of a row in the view is
- recorded (i.e., audited) in the emp_audit table. The current time
+ recorded (i.e., audited) in the emp_audit table. The current time
and user name are recorded, together with the type of operation
performed, and the view displays the last modified time of each row.
When the PostgreSQL return type is bytea, the
return value will be converted to a string (Python 2) or bytes
- (Python 3) using the respective Python builtins, with the
+ (Python 3) using the respective Python built-ins, with the
result being converted bytea.
For all other PostgreSQL return types, the returned Python
value is converted to a string using the Python
- builtin str, and the result is passed to the
+ built-in str, and the result is passed to the
input function of the PostgreSQL data type.
inserted into it. The subtransaction context manager does not
trap errors, it only assures that all database operations executed
inside its scope will be atomically committed or rolled back. A
- rollback of the subtransaction block occurrs on any kind of
+ rollback of the subtransaction block occurs on any kind of
exception exit, not only ones caused by errors originating from
database access. A regular Python exception raised inside an
explicit subtransaction block would also cause the subtransaction
top_regions and the output of top_regions
is used in the primary SELECT query.
This example could have been written without WITH,
- but we'd have needed two levels of nested sub-SELECTs. It's a bit
+ but we'd have needed two levels of nested sub-SELECTs. It's a bit
easier to follow this way.
sort_family_name
- The name (optionally schema-qualified) of an existing btree operator
+ The name (optionally schema-qualified) of an existing btree operator
family that describes the sort ordering associated with an ordering
operator.
- CLUSTER can re-sort the table using either an indexscan
+ CLUSTER can re-sort the table using either an index scan
on the specified index, or (if the index is a b-tree) a sequential
scan followed by sorting. It will attempt to choose the method that
will be faster, based on planner cost parameters and available statistical
- When an indexscan is used, a temporary copy of the table is created that
+ When an index scan is used, a temporary copy of the table is created that
contains the table data in the index order. Temporary copies of each
index on the table are created as well. Therefore, you need free space on
disk at least equal to the sum of the table size and the index sizes.
When a sequential scan and sort is used, a temporary sort file is
also created, so that the peak temporary space requirement is as much
as double the table size, plus the index sizes. This method is often
- faster than the indexscan method, but if the disk space requirement is
+ faster than the index scan method, but if the disk space requirement is
intolerable, you can disable this choice by temporarily setting
linkend="guc-enable-sort"> to off.
sort_family_name
- The name (optionally schema-qualified) of an existing btree operator
+ The name (optionally schema-qualified) of an existing btree operator
family that describes the sort ordering associated with an ordering
operator.
- If the optional boolean
+ If the optional Boolean
parameter collatable
is true, column definitions and expressions of the type may carry
collation information through use of
Do not use indicators but instead use special values to represent
- NULLs. Historically there have been databases using this approach.
+ null values. Historically there have been databases using this approach.
Prepare all statements before using them. Libecpg will keep a cache of
- prepared statments and reuse a statement if it gets executed again. If the
+ prepared statements and reuse a statement if it gets executed again. If the
cache runs full, libecpg will free the least used statement.
- Allow questionmark as placeholder for compatibility reasons.
+ Allow question mark as placeholder for compatibility reasons.
This used to be the default long ago.
- There can be multiple pg_basebackups running at the same time, but it is
+ There can be multiple pg_basebackups running at the same time, but it is
better from a performance point of view to take only one backup, and copy
the result.
Write the output as tar files in the target directory. The main
data directory will be written to a file named
base.tar, and all other tablespaces will
- be named after the tablespace oid.
+ be named after the tablespace OID.
If the value - (dash) is specified as
Enables verbose mode. Will output some extra steps during startup and
- shutdown, as well as show the exact filename that is currently being
+ shutdown, as well as show the exact file name that is currently being
processed if progress reporting is also enabled.
Output commands to clean (drop)
- database objects prior to outputing the commands for creating them.
+ database objects prior to outputting the commands for creating them.
(Restore might generate some harmless errors.)
- Add
client_hostname field to
+ Add
client_hostname field to
linkend="monitoring-stats-views-table">pg_stat_activity
(Peter Eisentraut)
Make EXPLAIN VERBOSE show the function call expression
- in a FunctionScan node (Tom Lane)
+ in a FunctionScan node (Tom Lane)
- These are used for xpath matching.
+ These are used for XPath matching.
- Allow ecpg to accept dynamic cursor names even in
+ Allow ECPG to accept dynamic cursor names even in
WHERE CURRENT OF clauses
- Enable building with the Mingw64 compiler (Andrew Dunstan)
+ Enable building with the MinGW64 compiler (Andrew Dunstan)
- Add missing get_{object}_oid() functions, for consistency
+ Add missing get_object_oid() functions, for consistency
(Robert Haas)
Allow
linkend="fuzzystrmatch">contrib/fuzzystrmatch's
- levenshtein() function handle multi-byte characters
+ levenshtein() function handle multibyte characters
(Alexander Korotkov)
/etc/rc.d/init.d/postgresql stop
See for details about starting and
- stoping the server.
+ stopping the server.
This module integrates with
SELinux to provide an- additional layer of security checking above and beyond what is normaly
+ additional layer of security checking above and beyond what is normally
provided by
PostgreSQL. From the perspective of
SELinux, this module allows
PostgreSQL to function as a user-space object
The following instructions that assume your installation is under the
/usr/local/pgsql directory. Adjust the paths shown below as
- appropriate for your installaton.
+ appropriate for your installation.
The xpath_table function assumes that the results of each XPath query
- might be multi-valued, so the number of rows returned by the function
+ might be multivalued, so the number of rows returned by the function
may not be the same as the number of input documents. The first row
returned contains the first result from each query, the second row the
second result from each query. If one of the queries has fewer values
{
ereport(ERROR,
(errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
- errmsg("unlogged GIST indexes are not supported")));
+ errmsg("unlogged GiST indexes are not supported")));
PG_RETURN_VOID();
}
* functions don't care about collation, so we just do it
* unconditionally. (We could alternatively call get_typcollation,
* but that seems like expensive overkill --- there aren't going to be
- * any cases where a GIST storage type has a nondefault collation.)
+ * any cases where a GiST storage type has a nondefault collation.)
*/
if (OidIsValid(index->rd_indcollation[i]))
giststate->supportCollation[i] = index->rd_indcollation[i];
int i;
if (GistPageIsLeaf(page)) /* shouldn't happen */
- elog(ERROR, "invalid GIST tuple found on leaf page");
+ elog(ERROR, "invalid GiST tuple found on leaf page");
for (i = 0; i < scan->numberOfOrderBys; i++)
so->distances[i] = -get_float8_infinity();
return true;
MemoryContext oldCxt;
/*
- * GIST indexes do not require any conflict processing. NB: If we ever
+ * GiST indexes do not require any conflict processing. NB: If we ever
* implement a similar optimization we have in b-tree, and remove killed
* tuples outside VACUUM, we'll need to handle that here.
*/
T053 Explicit aliases for all-fields reference NO
T061 UCS support NO
T071 BIGINT data type YES
-T101 Enhanced nullability determiniation NO
+T101 Enhanced nullability determination NO
T111 Updatable joins, unions, and columns NO
T121 WITH (excluding RECURSIVE) in query expression YES
T122 WITH (excluding RECURSIVE) in subquery YES
{
/*
* Hack to provide more-or-less-transparent updating of old RTREE
- * indexes to GIST: if RTREE is requested and not found, use GIST.
+ * indexes to GiST: if RTREE is requested and not found, use GIST.
*/
if (strcmp(accessMethodName, "rtree") == 0)
{
-- Detect missing pg_amproc entries: should have as many support functions
-- as AM expects for each datatype combination supported by the opfamily.
--- GIST/GIN are special cases because each has an optional support function.
+-- GiST/GIN are special cases because each has an optional support function.
SELECT p1.amname, p2.opfname, p3.amproclefttype, p3.amprocrighttype
FROM pg_am AS p1, pg_opfamily AS p2, pg_amproc AS p3
WHERE p2.opfmethod = p1.oid AND p3.amprocfamily = p2.oid AND
--------+---------+----------------+-----------------
(0 rows)
--- Similar check for GIST/GIN, allowing one optional proc
+-- Similar check for GiST/GIN, allowing one optional proc
SELECT p1.amname, p2.opfname, p3.amproclefttype, p3.amprocrighttype
FROM pg_am AS p1, pg_opfamily AS p2, pg_amproc AS p3
WHERE p2.opfmethod = p1.oid AND p3.amprocfamily = p2.oid AND
(0 rows)
-- Also, check if there are any pg_opclass entries that don't seem to have
--- pg_amproc support. Again, GIST/GIN have to be checked specially.
+-- pg_amproc support. Again, GiST/GIN have to be checked specially.
SELECT amname, opcname, count(*)
FROM pg_am am JOIN pg_opclass op ON opcmethod = am.oid
LEFT JOIN pg_amproc p ON amprocfamily = opcfamily AND
-- Detect missing pg_amproc entries: should have as many support functions
-- as AM expects for each datatype combination supported by the opfamily.
--- GIST/GIN are special cases because each has an optional support function.
+-- GiST/GIN are special cases because each has an optional support function.
SELECT p1.amname, p2.opfname, p3.amproclefttype, p3.amprocrighttype
FROM pg_am AS p1, pg_opfamily AS p2, pg_amproc AS p3
p4.amproclefttype = p3.amproclefttype AND
p4.amprocrighttype = p3.amprocrighttype);
--- Similar check for GIST/GIN, allowing one optional proc
+-- Similar check for GiST/GIN, allowing one optional proc
SELECT p1.amname, p2.opfname, p3.amproclefttype, p3.amprocrighttype
FROM pg_am AS p1, pg_opfamily AS p2, pg_amproc AS p3
NOT IN (p1.amsupport, p1.amsupport - 1);
-- Also, check if there are any pg_opclass entries that don't seem to have
--- pg_amproc support. Again, GIST/GIN have to be checked specially.
+-- pg_amproc support. Again, GiST/GIN have to be checked specially.
SELECT amname, opcname, count(*)
FROM pg_am am JOIN pg_opclass op ON opcmethod = am.oid
projects / postgresql.git / commitdiff