Use of symbolic references is enabled in a particular catalog column

by attaching <literal>BKI_LOOKUP(<replaceable>lookuprule</replaceable>)</literal>

to the column's definition, where <replaceable>lookuprule</replaceable>

is the name of the referenced catalog, e.g. <literal>pg_proc</literal>.

is the name of the referenced catalog, e.g., <literal>pg_proc</literal>.

<literal>BKI_LOOKUP</literal> can be attached to columns of

type <type>Oid</type>, <type>regproc</type>, <type>oidvector</type>,

or <type>Oid[]</type>; in the latter two cases it implies performing a

start with the <literal>.</literal> character are also ignored, to

prevent mistakes since such files are hidden on some platforms. Multiple

files within an include directory are processed in file name order

(according to C locale rules, i.e. numbers before letters, and

(according to C locale rules, i.e., numbers before letters, and

uppercase letters before lowercase ones).

</para>

<para>

With this parameter enabled, you can still create ordinary global

users. Simply append <literal>@</literal> when specifying the user

name in the client, e.g. <literal>joe@</literal>. The <literal>@</literal>

name in the client, e.g., <literal>joe@</literal>. The <literal>@</literal>

will be stripped off before the user name is looked up by the

server.

</para>

disabled, but the server continues to accumulate WAL segment files in

the expectation that a command will soon be provided. Setting

<varname>archive_command</varname> to a command that does nothing but

return true, e.g. <literal>/bin/true</literal> (<literal>REM</literal> on

return true, e.g., <literal>/bin/true</literal> (<literal>REM</literal> on

Windows), effectively disables

archiving, but also breaks the chain of WAL files needed for

archive recovery, so it should only be used in unusual circumstances.

<listitem>

<para>

This parameter specifies that recovery should end as soon as a

consistent state is reached, i.e. as early as possible. When restoring

consistent state is reached, i.e., as early as possible. When restoring

from an online backup, this means the point where taking the backup

ended.

</para>

<xref linkend="guc-timezone-abbreviations"/> variable has been set

earlier in the configuration file). Preferred style is to use a

numeric offset from UTC, or you can write a full time zone name,

e.g. <literal>Europe/Helsinki</literal> not <literal>EEST</literal>.

e.g., <literal>Europe/Helsinki</literal> not <literal>EEST</literal>.

</para>

</listitem>

</varlistentry>

if your data is likely to be completely in cache, such as when

the database is smaller than the total server memory, decreasing

random_page_cost can be appropriate. Storage that has a low random

read cost relative to sequential, e.g. solid-state drives, might

read cost relative to sequential, e.g., solid-state drives, might

also be better modeled with a lower value for random_page_cost,

e.g., <literal>1.1</literal>.

</para>

rows that can be locked; that value is unlimited. The default,

64, has historically proven sufficient, but you might need to

raise this value if you have queries that touch many different

tables in a single transaction, e.g. query of a parent table with

tables in a single transaction, e.g., query of a parent table with

many children. This parameter can only be set at server start.

</para>

with assertions enabled. That is the case if the

macro <symbol>USE_ASSERT_CHECKING</symbol> is defined

when <productname>PostgreSQL</productname> is built (accomplished

e.g. by the <command>configure</command> option

e.g., by the <command>configure</command> option

<option>--enable-cassert</option>). By

default <productname>PostgreSQL</productname> is built without

assertions.

very large number of digits. It is especially recommended for

storing monetary amounts and other quantities where exactness is

required. Calculations with <type>numeric</type> values yield exact

results where possible, e.g. addition, subtraction, multiplication.

results where possible, e.g., addition, subtraction, multiplication.

However, calculations on <type>numeric</type> values are very slow

compared to the integer types, or to the floating-point types

described in the next section.

<row>

<entry><type>unknown</type></entry>

<entry>Identifies a not-yet-resolved type, e.g. of an undecorated

<entry>Identifies a not-yet-resolved type, e.g., of an undecorated

string literal.</entry>

</row>

</tbody>

</para>

<para>

However, if the default value is volatile (e.g.

However, if the default value is volatile (e.g.,

<function>clock_timestamp()</function>)

each row will need to be updated with the value calculated at the time

<command>ALTER TABLE</command> is executed. To avoid a potentially

schema (assuming that the objects' own privilege requirements are

also met). Essentially this allows the grantee to <quote>look up</quote>

objects within the schema. Without this permission, it is still

possible to see the object names, e.g. by querying system catalogs.

possible to see the object names, e.g., by querying system catalogs.

Also, after revoking this permission, existing sessions might have

statements that have previously performed this lookup, so this is not

a completely secure way to prevent object access.

EXEC SQL FETCH NEXT FROM mycursor INTO SQL DESCRIPTOR mydesc;

</programlisting>

If the result set is empty, the Descriptor Area will still contain

the metadata from the query, i.e. the field names.

the metadata from the query, i.e., the field names.

</para>

<para>

<term><literal>sqllen</literal></term>

<listitem>

<para>

Contains the binary length of the field. e.g. 4 bytes for <type>ECPGt_int</type>.

Contains the binary length of the field. e.g., 4 bytes for <type>ECPGt_int</type>.

</para>

</listitem>

</varlistentry>

<term><literal>FREE cursor_name</literal></term>

<listitem>

<para>

Due to the differences how ECPG works compared to Informix's ESQL/C (i.e. which steps

Due to the differences how ECPG works compared to Informix's ESQL/C (i.e., which steps

are purely grammar transformations and which steps rely on the underlying run-time library)

there is no <literal>FREE cursor_name</literal> statement in ECPG. This is because in ECPG,

<literal>DECLARE CURSOR</literal> doesn't translate to a function call into

<para>

An extension is <firstterm>relocatable</firstterm> if it is possible to move

its contained objects into a different schema after initial creation

of the extension. The default is <literal>false</literal>, i.e. the

of the extension. The default is <literal>false</literal>, i.e., the

extension is not relocatable.

See <xref linkend="extend-extensions-relocation"/> for more information.

</para>

<term><varname>NO_INSTALLCHECK</varname></term>

<listitem>

<para>

don't define an <literal>installcheck</literal> target, useful e.g. if tests require special configuration, or don't use <application>pg_regress</application>

don't define an <literal>installcheck</literal> target, useful e.g., if tests require special configuration, or don't use <application>pg_regress</application>

</para>

</listitem>

</varlistentry>

<listitem>

<para>

In <function>to_timestamp</function> and <function>to_date</function>,

if the year format specification is less than four digits, e.g.

if the year format specification is less than four digits, e.g.,

<literal>YYY</literal>, and the supplied year is less than four digits,

the year will be adjusted to be nearest to the year 2020, e.g.

the year will be adjusted to be nearest to the year 2020, e.g.,

<literal>95</literal> becomes 1995.

</para>

</listitem>

<row>

<entry><literal>objsubid</literal></entry>

<entry><type>integer</type></entry>

<entry>Sub-object ID (e.g. attribute number for a column)</entry>

<entry>Sub-object ID (e.g., attribute number for a column)</entry>

</row>

<row>

<entry><literal>command_tag</literal></entry>

<row>

<entry><literal>objsubid</literal></entry>

<entry><type>integer</type></entry>

<entry>Sub-object ID (e.g. attribute number for a column)</entry>

<entry>Sub-object ID (e.g., attribute number for a column)</entry>

</row>

<row>

<entry><literal>original</literal></entry>

<glossdef>

<para>

Contains the values of <glossterm linkend="glossary-tuple">row</glossterm>

attributes (i.e. the data) for a

attributes (i.e., the data) for a

<glossterm linkend="glossary-relation">relation</glossterm>.

The heap is realized within one or more

<glossterm linkend="glossary-file-segment">file segments</glossterm>

this is unacceptable, either the middleware or the application

must query such values from a single server and then use those

values in write queries. Another option is to use this replication

option with a traditional primary-standby setup, i.e. data modification

option with a traditional primary-standby setup, i.e., data modification

queries are sent only to the primary and are propagated to the

standby servers via primary-standby replication, not by the replication

middleware. Care must also be taken that all

Set up continuous archiving on the primary to an archive directory

accessible from the standby, as described

in <xref linkend="continuous-archiving"/>. The archive location should be

accessible from the standby even when the primary is down, i.e. it should

accessible from the standby even when the primary is down, i.e., it should

reside on the standby server itself or another trusted server, not on

the primary server.

</para>

<itemizedlist>

<listitem>

<para>

Data Definition Language (DDL): e.g. <command>CREATE INDEX</command>

Data Definition Language (DDL): e.g., <command>CREATE INDEX</command>

</para>

</listitem>

<listitem>

<para>

WAL file control commands will not work during recovery,

e.g. <function>pg_start_backup</function>, <function>pg_switch_wal</function> etc.

e.g., <function>pg_start_backup</function>, <function>pg_switch_wal</function> etc.

</para>

<para>

linkend="indexes-index-only-scans"><firstterm>index-only scans</firstterm></link> on

the given column, by returning the indexed column values for an index entry

in the form of an <structname>IndexTuple</structname>. The attribute number

is 1-based, i.e. the first column's attno is 1. Returns true if supported,

is 1-based, i.e., the first column's attno is 1. Returns true if supported,

else false. If the access method does not support index-only scans at all,

the <structfield>amcanreturn</structfield> field in its <structname>IndexAmRoutine</structname>

struct can be set to NULL.