The above query only shows the rows from the inner query having
- rank> less than 3>.
+ rank> less than 3.
If any dimension is written as a slice, i.e., contains a colon, then all
dimensions are treated as slices. Any dimension that has only a single
- number (no colon) is treated as being from 1>
+ number (no colon) is treated as being from 1
to the number specified. For example, [2]> is treated as
[1:2]>, as in this example:
GNU
tar> return an error code indistinguishable from
a fatal error if a file was truncated while
tar> was
copying it. Fortunately, GNU
tar> versions 1.16 and
- later exit with 1> if a file was changed during the backup,
- and 2> for other errors.
+ later exit with 1 if a file was changed during the backup,
+ and 2 for other errors.
return the cast destination type as their result type. A cast
function can have up to three arguments. The second argument,
if present, must be type integer>; it receives the type
- modifier associated with the destination type, or -1>
+ modifier associated with the destination type, or -1
if there is none. The third argument,
if present, must be type boolean>; it receives true>
if the cast is an explicit cast, false> otherwise.
OID of the object within its system catalog, or null if the
object is not a general database object.
For advisory locks it is used to distinguish the two key
- spaces (1> for an int8 key, 2> for two
- int4 keys).
+ spaces (1 for an int8 key, 2 for two int4 keys).
|
include_realm
- If set to 1>, the realm name from the authenticated user
+ If set to 1, the realm name from the authenticated user
principal is included in the system user name that's passed through
user name mapping (). This is
useful for handling users from multiple realms.
include_realm
- If set to 1>, the realm name from the authenticated user
+ If set to 1, the realm name from the authenticated user
principal is included in the system user name that's passed through
user name mapping (). This is
useful for handling users from multiple realms.
include_realm
- If set to 1>, the realm name from the authenticated user
+ If set to 1, the realm name from the authenticated user
principal is included in the system user name that's passed through
user name mapping (). This is
useful for handling users from multiple realms.
ldaptls
- Set to 1> to make the connection between PostgreSQL and the
+ Set to 1 to make the connection between PostgreSQL and the
LDAP server use TLS encryption. Note that this only encrypts
the traffic to the LDAP server — the connection to the client
will still be unencrypted unless SSL is used.
A value of zero logs all temporary file information, while positive
values log only files whose size is greater than or equal to
the specified number of kilobytes. The
- default setting is -1>, which disables such logging.
+ default setting is -1, which disables such logging.
Only superusers can change this setting.
Specifies the cost delay value that will be used in automatic
- VACUUM> operations. If -1> is
- specified, the regular
+ VACUUM> operations. If -1 is specified, the regular
value will be used.
The default value is 20 milliseconds.
This parameter can only be set in the postgresql.conf>
Specifies the cost limit value that will be used in automatic
- VACUUM> operations. If -1> is specified (which is the
+ VACUUM> operations. If -1 is specified (which is the
default), the regular
value will be used. Note that
the value is distributed proportionally among the running autovacuum
match, the source> string is returned with the
replacement> string substituted for the matching
substring. The replacement> string can contain
- \>n>, where n> is 1>
- through 9>, to indicate that the source substring matching the
+ \>n>, where n> is 1
+ through 9, to indicate that the source substring matching the
n>'th parenthesized subexpression of the pattern should be
inserted, and it can contain \&> to indicate that the
substring matching the entire pattern should be inserted. Write
advised to select a larger value of max_locks_per_transaction>,
perhaps as much as twice the value of the parameter on
the primary server. You need not consider this at all if
- your setting of max_prepared_transactions> is 0>.
+ your setting of max_prepared_transactions> is 0.
function can only grow the tuples array one tuple at a time. But any
field of any existing tuple can be modified in any order. If a value at
field_num already exists, it will be overwritten.
value is
NULL>, the field value
will be set to an SQL null value. The
value is copied into the result's private storage,
certificates of the certificate authorities (
CAs)
you trust in the file root.crt in the data
directory, and set the clientcert parameter
- to 1 on the appropriate hostssl> line(s) in
+ to 1 on the appropriate hostssl> line(s) in
pg_hba.conf>.
A certificate will then be requested from the client during
SSL connection startup. (See for a
The clientcert option in pg_hba.conf> is
available for all authentication methods, but only for rows specified as
hostssl>. When clientcert is not specified
- or is set to 0>, the server will still verify presented client
+ or is set to 0, the server will still verify presented client
certificates against root.crt if that file exists
— but it will not insist that a client certificate be presented.
The count of expected arguments for the
plan.
If the
plan is
NULL or invalid,
SPI_result is set to SPI_ERROR_ARGUMENT
- and -1 is returned.
+ and -1 is returned.
due to failure to recreate the original
tsearch2>
objects. These errors can be ignored, but this means you cannot
restore the dump in a single transaction (eg, you cannot use
-
pg_restore>'s <literal>-1> switch).
+
pg_restore>'s <option>-1> switch).