Example: To keep 7 days of logs, one log file per day named
server_log.Mon, server_log.Tue,
- etc, and automatically overwrite last week's log with this week's log,
+ etc., and automatically overwrite last week's log with this week's log,
set log_filename to server_log.%a,
log_truncate_on_rotation to on, and
log_rotation_age to 1440.
alias
pg_temppg_temp. If it is not listed in the path then
it is searched first (even before pg_catalog). However,
the temporary schema is only searched for relation (table, view,
- sequence, etc) and data type names. It is never searched for
+ sequence, etc.) and data type names. It is never searched for
function or operator names.
PGresult to obtain information about the parameters
of the prepared statement, and the functions
, ,
- , etc provide information about the
+ , etc. provide information about the
result columns (if any) of the statement.
portal. On success, a PGresult with status
PGRES_COMMAND_OK is returned. The functions
, ,
- , etc can be applied to the
+ , etc. can be applied to the
PGresult to obtain information about the result
columns (if any) of the portal.
more rows will arrive. (But note that it is still necessary to continue
calling until it returns null.) All of
these PGresult objects will contain the same row
- description data (column names, types, etc) that an ordinary
+ description data (column names, types, etc.) that an ordinary
PGresult object for the query would have.
Each object should be freed with as usual.
0 indicates the overall copy format is textual (rows separated by
- newlines, columns separated by separator characters, etc). 1
+ newlines, columns separated by separator characters, etc.). 1
indicates the overall copy format is binary. See
linkend="sql-copy"/> for more information.
of data files. They are dependent on metadata contained in the main
data directory, and therefore cannot be attached to a different
database cluster or backed up individually. Similarly, if you lose
- a tablespace (file deletion, disk failure, etc), the database cluster
+ a tablespace (file deletion, disk failure, etc.), the database cluster
might become unreadable or unable to start. Placing a tablespace
on a temporary file system like a RAM disk risks the reliability of
the entire cluster.
spi_prepare, spi_query_prepared, spi_exec_prepared,
and spi_freeplan implement the same functionality but for prepared queries.
- spi_prepare accepts a query string with numbered argument placeholders ($1, $2, etc)
+ spi_prepare accepts a query string with numbered argument placeholders ($1, $2, etc.)
and a string list of argument types:
$plan = spi_prepare('SELECT * FROM test WHERE id > $1 AND name = $2',
2005-12-10 | 2005-12-11 | 2005-12-12
Note that the parameter subscript in spi_prepare is defined via
- $1, $2, $3, etc, so avoid declaring query strings in double quotes that might easily
+ $1, $2, $3, etc., so avoid declaring query strings in double quotes that might easily
lead to hard-to-catch bugs.
PL/Perl functions will share the same value of %_SHARED
if and only if they are executed by the same SQL role. In an application
wherein a single session executes code under multiple SQL roles (via
- SECURITY DEFINER functions, use of SET ROLE, etc)
+ SECURITY DEFINER functions, use of SET ROLE, etc.)
you may need to take explicit steps to ensure that PL/Perl functions can
share data via %_SHARED. To do that, make sure that
functions that should communicate are owned by the same user, and mark
functions will share the same global variables if and only if they are
executed by the same SQL role. In an application wherein a single
session executes code under multiple SQL roles (via SECURITY
- DEFINER functions, use of SET ROLE, etc) you may need to
+ DEFINER functions, use of SET ROLE, etc.) you may need to
take explicit steps to ensure that PL/Tcl functions can share data. To
do that, make sure that functions that should communicate are owned by
the same user, and mark them SECURITY DEFINER. You must of
on the public role. Keep in mind that the mapped
user can potentially use any client certificates,
.pgpass,
- .pg_service.conf etc in the unix home directory of the
+ .pg_service.conf etc. in the unix home directory of the
system user the postgres server runs as. They can also use any trust
relationship granted by authentication modes like peer
or ident authentication.
bind step, which creates a portal given a prepared
statement and values for any needed parameters; and an
execute step that runs a portal's query. In the case of
- a query that returns rows (SELECT, SHOW, etc),
+ a query that returns rows (SELECT, SHOW, etc.),
the execute step can be told to fetch only
a limited number of rows, so that multiple execute steps might be needed
to complete the operation.
Indicates that rows are about to be returned in response to
- a SELECT, FETCH, etc query.
+ a SELECT, FETCH, etc. query.
The contents of this message describe the column layout of the rows.
This will be followed by a DataRow message for each row being returned
to the frontend.
One of the set of rows returned by
- a SELECT, FETCH, etc query.
+ a SELECT, FETCH, etc. query.
0 indicates the overall COPY format is textual (rows
separated by newlines, columns separated by separator
- characters, etc).
+ characters, etc.).
1 indicates the overall copy format is binary (similar
to DataRow format).
See
0 indicates the overall COPY format
is textual (rows separated by newlines, columns
- separated by separator characters, etc). 1 indicates
+ separated by separator characters, etc.). 1 indicates
the overall copy format is binary (similar to DataRow
format). See for more information.
0 indicates the overall COPY format
is textual (rows separated by newlines, columns
- separated by separator characters, etc). 1 indicates
+ separated by separator characters, etc.). 1 indicates
the overall copy format is binary (similar to DataRow
format). See for more information.
SELECT. It is not required that the AS clause
specify names for all the columns, but it's good practice to do so.
(The default column names for VALUES are column1,
-
column2, etc in
PostgreSQL, but
+
column2, etc
. in
PostgreSQL, but
these names might be different in other database systems.)
- Layout rules (brace positioning, etc) follow BSD conventions. In
+ Layout rules (brace positioning, etc.) follow BSD conventions. In
particular, curly braces for the controlled blocks of if,
- while, switch, etc go on their own lines.
+ while, switch, etc. go on their own lines.
IS ISNULL NOTNULL
IS TRUE, IS FALSE, IS
- NULL, IS DISTINCT FROM, etc
+ NULL, IS DISTINCT FROM, etc.
|
described above; instead, a set-returning function could have at most
one set-returning argument, and each nest of set-returning functions
was run independently. Also, conditional execution (set-returning
- functions inside CASE etc) was previously allowed,
+ functions inside CASE etc.) was previously allowed,
complicating things even more.
Use of the LATERAL syntax is recommended when writing
queries that need to work in older
PostgreSQL versions,
just SELECT * — it can reference the output
columns by name or join them to other tables. The function produces a
virtual table with which you can perform any operation you wish (e.g.,
- aggregation, joining, sorting etc). So we could also have:
+ aggregation, joining, sorting etc.). So we could also have:
SELECT t.title, p.fullname, p.email
FROM xpath_table('article_id', 'article_xml', 'articles',
projects / postgresql.git / commitdiff