</programlisting>
The above query only shows the rows from the inner query having
- <literal>rank</> less than <literal>3</>.
+ <literal>rank</> less than 3.
</para>
<para>
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 <literal>1</>
+ number (no colon) is treated as being from 1
to the number specified. For example, <literal>[2]</> is treated as
<literal>[1:2]</>, as in this example:
GNU <application>tar</> return an error code indistinguishable from
a fatal error if a file was truncated while <application>tar</> was
copying it. Fortunately, GNU <application>tar</> versions 1.16 and
- later exit with <literal>1</> if a file was changed during the backup,
- and <literal>2</> for other errors.
+ later exit with 1 if a file was changed during the backup,
+ and 2 for other errors.
</para>
<para>
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 <type>integer</>; it receives the type
- modifier associated with the destination type, or <literal>-1</>
+ modifier associated with the destination type, or -1
if there is none. The third argument,
if present, must be type <type>boolean</>; it receives <literal>true</>
if the cast is an explicit cast, <literal>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 (<literal>1</> for an int8 key, <literal>2</> for two
- int4 keys).
+ spaces (1 for an int8 key, 2 for two int4 keys).
</entry>
</row>
<row>
<term><literal>include_realm</literal></term>
<listitem>
<para>
- If set to <literal>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 (<xref linkend="auth-username-maps">). This is
useful for handling users from multiple realms.
<term><literal>include_realm</literal></term>
<listitem>
<para>
- If set to <literal>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 (<xref linkend="auth-username-maps">). This is
useful for handling users from multiple realms.
<term><literal>include_realm</literal></term>
<listitem>
<para>
- If set to <literal>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 (<xref linkend="auth-username-maps">). This is
useful for handling users from multiple realms.
<term><literal>ldaptls</literal></term>
<listitem>
<para>
- Set to <literal>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 <literal>-1</>, which disables such logging.
+ default setting is -1, which disables such logging.
Only superusers can change this setting.
</para>
</listitem>
<listitem>
<para>
Specifies the cost delay value that will be used in automatic
- <command>VACUUM</> operations. If <literal>-1</> is
- specified, the regular
+ <command>VACUUM</> operations. If -1 is specified, the regular
<xref linkend="guc-vacuum-cost-delay"> value will be used.
The default value is 20 milliseconds.
This parameter can only be set in the <filename>postgresql.conf</>
<listitem>
<para>
Specifies the cost limit value that will be used in automatic
- <command>VACUUM</> operations. If <literal>-1</> is specified (which is the
+ <command>VACUUM</> operations. If -1 is specified (which is the
default), the regular
<xref linkend="guc-vacuum-cost-limit"> value will be used. Note that
the value is distributed proportionally among the running autovacuum
match, the <replaceable>source</> string is returned with the
<replaceable>replacement</> string substituted for the matching
substring. The <replaceable>replacement</> string can contain
- <literal>\</><replaceable>n</>, where <replaceable>n</> is <literal>1</>
- through <literal>9</>, to indicate that the source substring matching the
+ <literal>\</><replaceable>n</>, where <replaceable>n</> is 1
+ through 9, to indicate that the source substring matching the
<replaceable>n</>'th parenthesized subexpression of the pattern should be
inserted, and it can contain <literal>\&</> to indicate that the
substring matching the entire pattern should be inserted. Write
advised to select a larger value of <varname>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 <varname>max_prepared_transactions</> is <literal>0</>.
+ your setting of <varname>max_prepared_transactions</> is 0.
</para>
</listitem>
</itemizedlist>
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
<parameter>field_num</parameter> already exists, it will be overwritten.
- If <parameter>len</parameter> is <literal>-1</literal> or
+ If <parameter>len</parameter> is -1 or
<parameter>value</parameter> is <symbol>NULL</>, the field value
will be set to an SQL null value. The
<parameter>value</parameter> is copied into the result's private storage,
certificates of the certificate authorities (<acronym>CA</acronym>s)
you trust in the file <filename>root.crt</filename> in the data
directory, and set the <literal>clientcert</literal> parameter
- to <literal>1</literal> on the appropriate <literal>hostssl</> line(s) in
+ to 1 on the appropriate <literal>hostssl</> line(s) in
<filename>pg_hba.conf</>.
A certificate will then be requested from the client during
SSL connection startup. (See <xref linkend="libpq-ssl"> for a
The <literal>clientcert</literal> option in <filename>pg_hba.conf</> is
available for all authentication methods, but only for rows specified as
<literal>hostssl</>. When <literal>clientcert</literal> is not specified
- or is set to <literal>0</>, the server will still verify presented client
+ or is set to 0, the server will still verify presented client
certificates against <filename>root.crt</filename> if that file exists
— but it will not insist that a client certificate be presented.
</para>
The count of expected arguments for the <parameter>plan</parameter>.
If the <parameter>plan</parameter> is <symbol>NULL</symbol> or invalid,
<varname>SPI_result</varname> is set to <symbol>SPI_ERROR_ARGUMENT</symbol>
- and <literal>-1</literal> is returned.
+ and -1 is returned.
</para>
</refsect1>
</refentry>
due to failure to recreate the original <application>tsearch2</>
objects. These errors can be ignored, but this means you cannot
restore the dump in a single transaction (eg, you cannot use
- <application>pg_restore</>'s <literal>-1</> switch).
+ <application>pg_restore</>'s <option>-1</> switch).
</para>
</step>
projects / users / hanada / postgres.git / commitdiff