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>@</> when specifying the user

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

name in the client, e.g., <literal>joe@</>. The <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</> to a command that does nothing but

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

return true, e.g., <literal>/bin/true</> (<literal>REM</> 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.

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</></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>

<para>

An object can be assigned to a new owner with an <command>ALTER</command>

command of the appropriate kind for the object, e.g. <xref

command of the appropriate kind for the object, e.g., <xref

linkend="sql-altertable">. Superusers can always do

this; ordinary roles can only do it if they are both the current owner

of the object (or a member of the owning role) and a member of the new

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</></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</></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</> 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</> if it is possible to move

its contained objects into a different schema after initial creation

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

of the extension. The default is <literal>false</>, 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>

will be replaced by the year data, but the single <literal>Y</literal> in <literal>Year</literal>

will not be. In <function>to_date</>, <function>to_number</>,

and <function>to_timestamp</>, double-quoted strings skip the number of

input characters contained in the string, e.g. <literal>"XX"</>

input characters contained in the string, e.g., <literal>"XX"</>

skips two input characters.

</para>

</listitem>

<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</>, 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</> 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>

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 master-standby setup, i.e. data modification

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

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

standby servers via master-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 master is down, i.e. it should

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

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

the master server.

</para>

<itemizedlist>

<listitem>

<para>

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

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

</para>

</listitem>

<listitem>

<para>

WAL file control commands will not work during recovery,

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

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

</para>

<para>

linkend="indexes-index-only-scans"><firstterm>index-only scans</></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</> field in its <structname>IndexAmRoutine</>

struct can be set to NULL.

In the <productname>Microsoft Windows SDK</productname>, start the

<application>CMD shell</application> listed under the SDK on the Start Menu.

In recent SDK versions you can change the targeted CPU architecture, build

type, and target OS by using the <command>setenv</command> command, e.g.

type, and target OS by using the <command>setenv</command> command, e.g.,

<command>setenv /x86 /release /xp</command> to target Windows XP or later

with a 32-bit release build. See <command>/?</command> for other options to

<command>setenv</command>. All commands should be run from the

installations <filename>C:\Program Files\GnuWin32</filename>.

Consider installing into <filename>C:\GnuWin32</filename> or use the

NTFS short name path to GnuWin32 in your PATH environment setting

(e.g. <filename>C:\PROGRA~1\GnuWin32</filename>).

(e.g., <filename>C:\PROGRA~1\GnuWin32</filename>).

</para>

</note>

Conversely, if <function>PQconnectPoll(conn)</function> last returned

<symbol>PGRES_POLLING_WRITING</symbol>, wait until the socket is ready

to write, then call <function>PQconnectPoll(conn)</function> again.

On the first iteration, i.e. if you have yet to call

On the first iteration, i.e., if you have yet to call

<function>PQconnectPoll</function>, behave as if it last returned

<symbol>PGRES_POLLING_WRITING</symbol>. Continue this loop until

<function>PQconnectPoll(conn)</function> returns

<para>

Percent-encoding may be used to include symbols with special meaning in any

of the <acronym>URI</acronym> parts, e.g. replace <literal>=</> with

of the <acronym>URI</acronym> parts, e.g., replace <literal>=</> with

<literal>%3D</>.

</para>

<literal>hostaddr</>, and <literal>port</> options accept a comma-separated

list of values. The same number of elements must be given in each

option that is specified, such

that e.g. the first <literal>hostaddr</> corresponds to the first host name,

that e.g., the first <literal>hostaddr</> corresponds to the first host name,

the second <literal>hostaddr</> corresponds to the second host name, and so

forth. As an exception, if only one <literal>port</literal> is specified, it

applies to all the hosts.

<para>

If a password file is used, you can have different passwords for

different hosts. All the other connection options are the same for every

host in the list; it is not possible to e.g. specify different

host in the list; it is not possible to e.g., specify different

usernames for different hosts.

</para>

</sect3>

<listitem>

<para>

Maximum wait for connection, in seconds (write as a decimal integer,

e.g. <literal>10</literal>). Zero, negative, or not specified means

e.g., <literal>10</literal>). Zero, negative, or not specified means

wait indefinitely. The minimum allowed timeout is 2 seconds, therefore

a value of <literal>1</literal> is interpreted as <literal>2</literal>.

This timeout applies separately to each host name or IP address.

<term><literal>cipher</literal></term>

<listitem>

<para>

A short name of the ciphersuite used, e.g.

A short name of the ciphersuite used, e.g.,

<literal>"DHE-RSA-DES-CBC3-SHA"</literal>. The names are specific

to each SSL implementation.

</para>

<function>PQflush</function> again. Repeat until

<function>PQflush</function> returns 0. (It is necessary to check for

read-ready and drain the input with <function>PQconsumeInput</function>,

because the server can block trying to send us data, e.g. NOTICE

because the server can block trying to send us data, e.g., NOTICE

messages, and won't read our data until we read its.) Once

<function>PQflush</function> returns 0, wait for the socket to be

read-ready and then read the response as described above.

For a connection to be known secure, SSL usage must be configured

on <emphasis>both the client and the server</> before the connection

is made. If it is only configured on the server, the client may end up

sending sensitive information (e.g. passwords) before

sending sensitive information (e.g., passwords) before

it knows that the server requires high security. In libpq, secure

connections can be ensured

by setting the <literal>sslmode</> parameter to <literal>verify-full</> or