fi

PGPRO_VERSION="$PACKAGE_VERSION.1"

PGPRO_VERSION="$PACKAGE_VERSION.2"

PGPRO_PACKAGE_NAME="PostgresPro"

PGPRO_EDITION="standard"

_ACEOF

if test x"$HAVE_LONG_LONG_INT_64" = xyes ; then

cat confdefs.h - <<_ACEOF >conftest.$ac_ext

/* end confdefs.h. */

#define INT64CONST(x) x##LL

long long int foo = INT64CONST(0x1234567890123456);

_ACEOF

if ac_fn_c_try_compile "$LINENO"; then :

$as_echo "#define HAVE_LL_CONSTANTS 1" >>confdefs.h

fi

rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext

fi

# If we found "long int" is 64 bits, assume snprintf handles it. If

# we found we need to use "long long int", better check. We cope with

# snprintfs that use %lld, %qd, or %I64d as the format. If none of these

PGAC_ARG_REQ(with, extra-version, [STRING], [append STRING to version],

[PG_VERSION="$PACKAGE_VERSION$withval"],

[PG_VERSION="$PACKAGE_VERSION"])

PGPRO_VERSION="$PACKAGE_VERSION.1"

PGPRO_VERSION="$PACKAGE_VERSION.2"

PGPRO_PACKAGE_NAME="PostgresPro"

PGPRO_EDITION="standard"

AC_SUBST(PGPRO_PACKAGE_NAME)

AC_DEFINE_UNQUOTED(PG_INT64_TYPE, $pg_int64_type,

[Define to the name of a signed 64-bit integer type.])

dnl If we need to use "long long int", figure out whether nnnLL notation works.

if test x"$HAVE_LONG_LONG_INT_64" = xyes ; then

AC_COMPILE_IFELSE([AC_LANG_SOURCE([

#define INT64CONST(x) x##LL

long long int foo = INT64CONST(0x1234567890123456);

])],

[AC_DEFINE(HAVE_LL_CONSTANTS, 1, [Define to 1 if constants of type 'long long int' should have the suffix LL.])],

[])

fi

# If we found "long int" is 64 bits, assume snprintf handles it. If

# we found we need to use "long long int", better check. We cope with

# snprintfs that use %lld, %qd, or %I64d as the format. If none of these

<programlisting>

SELECT * FROM pg_stop_backup(false);

</programlisting>

This terminates the backup mode and performs an automatic switch to

the next WAL segment. The reason for the switch is to arrange for

This terminates backup mode. On a primary, it also performs an automatic

switch to the next WAL segment. On a standby, it is not possible to

automatically switch WAL segments, so you may wish to run

<function>pg_switch_xlog</function> on the primary to perform a manual

switch. The reason for the switch is to arrange for

the last WAL segment file written during the backup interval to be

ready to archive.

</para>

Once the WAL segment files active during the backup are archived, you are

done. The file identified by <function>pg_stop_backup</>'s first return

value is the last segment that is required to form a complete set of

backup files.If <varname>archive_mode</> is enabled,

backup files.On a primary, if <varname>archive_mode</> is enabled,

<function>pg_stop_backup</> does not return until the last segment has

been archived.

Archiving of these files happens automatically since you have

<function>pg_stop_backup</> terminates because of this your backup

may not be valid.

</para>

<para>

Note that on a standby <function>pg_stop_backup</> does not wait for

WAL segments to be archived so the backup process must ensure that all WAL

segments required for the backup are successfully archived.

</para>

</listitem>

</orderedlist>

</para>

<title>Making an exclusive low level backup</title>

<para>

The process for an exclusive backup is mostly the same as for a

non-exclusive one, but it differs in a few key steps.It does not allow

more than one concurrent backup to run, andthere can be some issues on

the server if it crashes during the backup.Prior to&productname; 9.6, this

non-exclusive one, but it differs in a few key steps.This type of backup

can only be taken on a primary anddoes not allow concurrent backups.

Prior to<productname>PostgreSQL</> 9.6, this

was the only low-level method available, but it is now recommended that

all users upgrade their scripts to use non-exclusive backups if possible.

</para>

<xref linkend="backup-lowlevel-base-backup-data"> for things to

consider during this backup.

</para>

<para>

Note that if the server crashes during the backup it may not be

possible to restart until the <literal>backup_label</> file has been

manually deleted from the <envar>PGDATA</envar> directory.

</para>

</listitem>

<listitem>

<para>

<entry align="center"><literal>X</literal></entry>

<entry align="center"><literal>-</literal></entry>

<entry align="center"><literal>-</literal></entry>

<entry align="center"></entry>

</row>

<row>

<entry align="left"><literal>CREATE USER MAPPING</literal></entry>

<tbody>

<row>

<entry><literal>9</literal></entry>

<entry>value with the specified number of digits</entry>

<entry>digit position (can be dropped if insignificant)</entry>

</row>

<row>

<entry><literal>0</literal></entry>

<entry>value with leading zeros</entry>

<entry>digit position (will not be dropped, even if insignificant)</entry>

</row>

<row>

<entry><literal>.</literal> (period)</entry>

<entry>decimal point</entry>

</row>

<row>

<entry><literal>,</literal> (comma)</entry>

<entry>group (thousand) separator</entry>

<entry>group (thousands) separator</entry>

</row>

<row>

<entry><literal>PR</literal></entry>

Usage notes for numeric formatting:

<itemizedlist>

<listitem>

<para>

<literal>0</> specifies a digit position that will always be printed,

even if it contains a leading/trailing zero. <literal>9</> also

specifies a digit position, but if it is a leading zero then it will

be replaced by a space, while if it is a trailing zero and fill mode

is specified then it will be deleted. (For <function>to_number()</>,

these two pattern characters are equivalent.)

</para>

</listitem>

<listitem>

<para>

The pattern characters <literal>S</>, <literal>L</>, <literal>D</>,

and <literal>G</> represent the sign, currency symbol, decimal point,

and thousands separator characters defined by the current locale

(see <xref linkend="guc-lc-monetary">

and <xref linkend="guc-lc-numeric">). The pattern characters period

and comma represent those exact characters, with the meanings of

decimal point and thousands separator, regardless of locale.

</para>

</listitem>

<listitem>

<para>

If no explicit provision is made for a sign

in <function>to_char()</>'s pattern, one column will be reserved for

the sign, and it will be anchored to (appear just left of) the

number. If <literal>S</> appears just left of some <literal>9</>'s,

it will likewise be anchored to the number.

</para>

</listitem>

<listitem>

<para>

A sign formatted using <literal>SG</literal>, <literal>PL</literal>, or

<literal>MI</literal> is not anchored to

the number; for example,

<literal>to_char(-12, 'MI9999')</literal> produces <literal>'-&nbsp;&nbsp;12'</literal>

but <literal>to_char(-12, 'S9999')</literal> produces <literal>'&nbsp;&nbsp;-12'</literal>.

The Oracle implementation does not allow the use of

(The Oracle implementation does not allow the use of

<literal>MI</literal> before <literal>9</literal>, but rather

requires that <literal>9</literal> precede

<literal>MI</literal>.

</para>

</listitem>

<listitem>

<para>

<literal>9</literal> results in a value with the same number of

digits as there are <literal>9</literal>s. If a digit is

not available it outputs a space.

<literal>MI</literal>.)

</para>

</listitem>

<para>

Certain modifiers can be applied to any template pattern to alter its

behavior. For example, <literal>FM9999</literal>

is the <literal>9999</literal> pattern with the

behavior. For example, <literal>FM99.99</literal>

is the <literal>99.99</literal> pattern with the

<literal>FM</literal> modifier.

<xref linkend="functions-formatting-numericmod-table"> shows the

modifier patterns for numeric formatting.

<tbody>

<row>

<entry><literal>FM</literal> prefix</entry>

<entry>fill mode (suppressleading zeroes and padding blanks)</entry>

<entry><literal>FM9999</literal></entry>

<entry>fill mode (suppresstrailing zeroes and padding blanks)</entry>

<entry><literal>FM99.99</literal></entry>

</row>

<row>

<entry><literal>TH</literal> suffix</entry>

<entry><literal>to_char(-0.1, 'FM9.99')</literal></entry>

<entry><literal>'-.1'</literal></entry>

</row>

<row>

<entry><literal>to_char(-0.1, 'FM90.99')</literal></entry>

<entry><literal>'-0.1'</literal></entry>

</row>

<row>

<entry><literal>to_char(0.1, '0.9')</literal></entry>

<entry><literal>'&nbsp;0.1'</literal></entry>

<function>pg_start_backup</>. In a non-exclusive backup, the contents of

the <filename>backup_label</> and <filename>tablespace_map</> are returned

in the result of the function, and should be written to files in the

backup (and not in the data directory).

backup (and not in the data directory). When executed on a primary

<function>pg_stop_backup</> will wait for WAL to be archived, provided that

archiving is enabled.

</para>

<para>

On a standby <function>pg_stop_backup</> will return immediately without

waiting, so it's important to verify that all required WAL segments have

been archived. If write activity on the primary is low, it may be useful

to run <function>pg_switch_xlog</> on the primary in order to trigger a

segment switch.

</para>

<para>

The function also creates a backup history file in the transaction log

When executed on a primary, the function also creates a backup history file

in the write-ahead log

archive area. The history file includes the label given to

<function>pg_start_backup</>, the starting and ending transaction log locations for

the backup, and the starting and ending times of the backup. The return

<listitem>

<para>

Returns the number of rows (tuples) in the query result. Because

it returns an integer result, large result sets might overflow the

return value on 32-bit operating systems.

Returns the number of rows (tuples) in the query result.

(Note that <structname>PGresult</> objects are limited to no more

than <literal>INT_MAX</> rows, so an <type>int</> result is

sufficient.)

<synopsis>

int PQntuples(const PGresult *res);

<para>

The <link linkend="view-pg-replication-slots"><structname>pg_replication_slots</structname></link>

view and the

<link linkend="monitoring-stats-views-table"><structname>pg_stat_replication</structname></link>

<link linkend="pg-stat-replication-view"><structname>pg_stat_replication</structname></link>

view provide information about the current state of replication slots and

streaming replication connections respectively. These views apply to both physical and

logical replication.

<listitem>

<para>

Increase <xref linkend="guc-max-wal-size"> and <xref

linkend="guc-checkpoint-timeout">; this reduces the frequency

linkend="guc-checkpoint-timeout">; this reduces the frequency

of checkpoints, but increases the storage requirements of

<filename>/pg_xlog</>.

</para>

char*filename;

intfilenamelen;

int64chunkoff;

charchunkoff_str[32];

intchunksize;

char*chunk;

continue;

}

pg_log(PG_DEBUG,"received chunk for file \"%s\", offset "INT64_FORMAT", size %d\n",

filename,chunkoff,chunksize);

snprintf(chunkoff_str,sizeof(chunkoff_str),INT64_FORMAT,chunkoff);

pg_log(PG_DEBUG,"received chunk for file \"%s\", offset %s, size %d\n",

filename,chunkoff_str,chunksize);

open_target_file(filename, false);

typedefunsigned longintuint64;

#defineINT64CONST(x) (x##L)

#defineUINT64CONST(x) (x##UL)

#elif defined(HAVE_LONG_LONG_INT_64)

typedefunsigned long longintuint64;

#defineINT64CONST(x) (x##LL)

#defineUINT64CONST(x) (x##ULL)

#error must have a working 64-bit integer datatype

#defineINT64CONST(x) ((int64) x##LL)

#defineUINT64CONST(x) ((uint64) x##ULL)

#defineINT64CONST(x) ((int64) x)

#defineUINT64CONST(x) ((uint64) x)

#defineINT64_FORMAT "%" INT64_MODIFIER "d"

#defineUINT64_FORMAT "%" INT64_MODIFIER "u"

#definePG_UINT16_MAX(0xFFFF)

#definePG_INT32_MIN(-0x7FFFFFFF-1)

#definePG_INT32_MAX(0x7FFFFFFF)

#definePG_UINT32_MAX(0xFFFFFFFF)

#definePG_UINT32_MAX(0xFFFFFFFFU)

#definePG_INT64_MIN(-INT64CONST(0x7FFFFFFFFFFFFFFF) - 1)

#definePG_INT64_MAXINT64CONST(0x7FFFFFFFFFFFFFFF)

#definePG_UINT64_MAXUINT64CONST(0xFFFFFFFFFFFFFFFF)

#defineSIZE_MAX PG_UINT64_MAX

#defineSIZE_MAX PG_UINT32_MAX