2014-03-18 18:20:01 +01:00
|
|
|
<!--
|
|
|
|
doc/src/sgml/ref/pg_recvlogical.sgml
|
|
|
|
PostgreSQL documentation
|
|
|
|
-->
|
|
|
|
|
|
|
|
<refentry id="app-pgrecvlogical">
|
2014-05-07 03:28:58 +02:00
|
|
|
<indexterm zone="app-pgrecvlogical">
|
|
|
|
<primary>pg_recvlogical</primary>
|
|
|
|
</indexterm>
|
|
|
|
|
2014-03-18 18:20:01 +01:00
|
|
|
<refmeta>
|
|
|
|
<refentrytitle><application>pg_recvlogical</application></refentrytitle>
|
|
|
|
<manvolnum>1</manvolnum>
|
|
|
|
<refmiscinfo>Application</refmiscinfo>
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
<refnamediv>
|
|
|
|
<refname>pg_recvlogical</refname>
|
2014-10-18 15:10:12 +02:00
|
|
|
<refpurpose>control <productname>PostgreSQL</productname> logical decoding streams</refpurpose>
|
2014-03-18 18:20:01 +01:00
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
|
|
|
<cmdsynopsis>
|
|
|
|
<command>pg_recvlogical</command>
|
2014-10-18 15:10:12 +02:00
|
|
|
<arg rep="repeat" choice="opt"><replaceable>option</replaceable></arg>
|
2014-03-18 18:20:01 +01:00
|
|
|
</cmdsynopsis>
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
2014-10-18 15:10:12 +02:00
|
|
|
<refsect1>
|
2014-03-18 18:20:01 +01:00
|
|
|
<title>Description</title>
|
|
|
|
<para>
|
|
|
|
<command>pg_recvlogical</command> controls logical decoding replication
|
|
|
|
slots and streams data from such replication slots.
|
|
|
|
</para>
|
2014-10-18 15:10:12 +02:00
|
|
|
|
2014-03-18 18:20:01 +01:00
|
|
|
<para>
|
|
|
|
It creates a replication-mode connection, so it is subject to the same
|
2017-11-23 15:39:47 +01:00
|
|
|
constraints as <xref linkend="app-pgreceivewal"/>, plus those for logical
|
|
|
|
replication (see <xref linkend="logicaldecoding"/>).
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
2017-01-04 20:02:07 +01:00
|
|
|
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
<command>pg_recvlogical</command> has no equivalent to the logical decoding
|
2017-01-04 20:02:07 +01:00
|
|
|
SQL interface's peek and get modes. It sends replay confirmations for
|
|
|
|
data lazily as it receives it and on clean exit. To examine pending data on
|
|
|
|
a slot without consuming it, use
|
2017-10-09 03:44:17 +02:00
|
|
|
<link linkend="functions-replication"><function>pg_logical_slot_peek_changes</function></link>.
|
2017-01-04 20:02:07 +01:00
|
|
|
</para>
|
2022-09-14 16:32:24 +02:00
|
|
|
|
|
|
|
<para>
|
|
|
|
In the absence of fatal errors, <application>pg_recvlogical</application>
|
|
|
|
will run until terminated by the <systemitem>SIGINT</systemitem>
|
|
|
|
(<keycombo action="simul"><keycap>Control</keycap><keycap>C</keycap></keycombo>)
|
|
|
|
or <systemitem>SIGTERM</systemitem> signal.
|
|
|
|
</para>
|
2014-03-18 18:20:01 +01:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Options</title>
|
|
|
|
|
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
At least one of the following options must be specified to select an action:
|
2014-03-18 18:20:01 +01:00
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
|
|
|
|
<varlistentry>
|
2014-10-06 12:11:52 +02:00
|
|
|
<term><option>--create-slot</option></term>
|
2014-03-18 18:20:01 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
Create a new logical replication slot with the name specified by
|
|
|
|
<option>--slot</option>, using the output plugin specified by
|
|
|
|
<option>--plugin</option>, for the database specified
|
|
|
|
by <option>--dbname</option>.
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
2021-06-30 05:15:47 +02:00
|
|
|
|
|
|
|
<para>
|
|
|
|
The <option>--two-phase</option> can be specified with
|
|
|
|
<option>--create-slot</option> to enable two-phase decoding.
|
|
|
|
</para>
|
2014-03-18 18:20:01 +01:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2014-10-18 15:10:12 +02:00
|
|
|
<term><option>--drop-slot</option></term>
|
2014-03-18 18:20:01 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
Drop the replication slot with the name specified
|
|
|
|
by <option>--slot</option>, then exit.
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2014-10-18 15:10:12 +02:00
|
|
|
<term><option>--start</option></term>
|
2014-03-18 18:20:01 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
Begin streaming changes from the logical replication slot specified
|
|
|
|
by <option>--slot</option>, continuing until terminated by a
|
|
|
|
signal. If the server side change stream ends with a server shutdown
|
|
|
|
or disconnect, retry in a loop unless
|
|
|
|
<option>--no-loop</option> is specified.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The stream format is determined by the output plugin specified when
|
|
|
|
the slot was created.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The connection must be to the same database used to create the slot.
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
<option>--create-slot</option> and <option>--start</option> can be
|
|
|
|
specified together. <option>--drop-slot</option> cannot be combined with
|
|
|
|
another action.
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The following command-line options control the location and format of the
|
2014-07-17 04:20:15 +02:00
|
|
|
output and other replication behavior:
|
2014-03-18 18:20:01 +01:00
|
|
|
|
|
|
|
<variablelist>
|
2017-06-08 18:12:31 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-E <replaceable>lsn</replaceable></option></term>
|
|
|
|
<term><option>--endpos=<replaceable>lsn</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
In <option>--start</option> mode, automatically stop replication
|
|
|
|
and exit with normal exit status 0 when receiving reaches the
|
|
|
|
specified LSN. If specified when not in <option>--start</option>
|
|
|
|
mode, an error is raised.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
If there's a record with LSN exactly equal to <replaceable>lsn</replaceable>,
|
2017-06-08 18:12:31 +02:00
|
|
|
the record will be output.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The <option>--endpos</option> option is not aware of transaction
|
|
|
|
boundaries and may truncate output partway through a transaction.
|
|
|
|
Any partially output transaction will not be consumed and will be
|
|
|
|
replayed again when the slot is next read from. Individual messages
|
|
|
|
are never truncated.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2014-03-18 18:20:01 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-f <replaceable>filename</replaceable></option></term>
|
|
|
|
<term><option>--file=<replaceable>filename</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Write received and decoded transaction data into this
|
2017-10-09 03:44:17 +02:00
|
|
|
file. Use <literal>-</literal> for <systemitem>stdout</systemitem>.
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2014-10-18 15:10:12 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-F <replaceable>interval_seconds</replaceable></option></term>
|
|
|
|
<term><option>--fsync-interval=<replaceable>interval_seconds</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Specifies how often <application>pg_recvlogical</application> should
|
|
|
|
issue <function>fsync()</function> calls to ensure the output file is
|
|
|
|
safely flushed to disk.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The server will occasionally request the client to perform a flush and
|
|
|
|
report the flush position to the server. This setting is in addition
|
|
|
|
to that, to perform flushes more frequently.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Specifying an interval of <literal>0</literal> disables
|
|
|
|
issuing <function>fsync()</function> calls altogether, while still
|
|
|
|
reporting progress to the server. In this case, data could be lost in
|
|
|
|
the event of a crash.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2014-03-18 18:20:01 +01:00
|
|
|
|
|
|
|
<varlistentry>
|
2014-10-18 15:10:12 +02:00
|
|
|
<term><option>-I <replaceable>lsn</replaceable></option></term>
|
|
|
|
<term><option>--startpos=<replaceable>lsn</replaceable></option></term>
|
2014-03-18 18:20:01 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
In <option>--start</option> mode, start replication from the given
|
|
|
|
LSN. For details on the effect of this, see the documentation
|
2017-11-23 15:39:47 +01:00
|
|
|
in <xref linkend="logicaldecoding"/>
|
|
|
|
and <xref linkend="protocol-replication"/>. Ignored in other modes.
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2015-07-12 22:06:27 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>--if-not-exists</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2016-07-20 10:39:18 +02:00
|
|
|
Do not error out when <option>--create-slot</option> is specified
|
2015-07-12 22:06:27 +02:00
|
|
|
and a slot with the specified name already exists.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2014-03-18 18:20:01 +01:00
|
|
|
<varlistentry>
|
2014-10-18 15:10:12 +02:00
|
|
|
<term><option>-n</option></term>
|
|
|
|
<term><option>--no-loop</option></term>
|
2014-03-18 18:20:01 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
When the connection to the server is lost, do not retry in a loop, just exit.
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2014-10-18 15:10:12 +02:00
|
|
|
<term><option>-o <replaceable>name</replaceable>[=<replaceable>value</replaceable>]</option></term>
|
|
|
|
<term><option>--option=<replaceable>name</replaceable>[=<replaceable>value</replaceable>]</option></term>
|
2014-03-18 18:20:01 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
Pass the option <replaceable>name</replaceable> to the output plugin with,
|
|
|
|
if specified, the option value <replaceable>value</replaceable>. Which
|
|
|
|
options exist and their effects depends on the used output plugin.
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><option>-P <replaceable>plugin</replaceable></option></term>
|
|
|
|
<term><option>--plugin=<replaceable>plugin</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
When creating a slot, use the specified logical decoding output
|
2017-11-23 15:39:47 +01:00
|
|
|
plugin. See <xref linkend="logicaldecoding"/>. This option has no
|
2014-03-18 18:20:01 +01:00
|
|
|
effect if the slot already exists.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><option>-s <replaceable>interval_seconds</replaceable></option></term>
|
|
|
|
<term><option>--status-interval=<replaceable>interval_seconds</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
This option has the same effect as the option of the same name
|
2017-11-23 15:39:47 +01:00
|
|
|
in <xref linkend="app-pgreceivewal"/>. See the description there.
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><option>-S <replaceable>slot_name</replaceable></option></term>
|
|
|
|
<term><option>--slot=<replaceable>slot_name</replaceable></option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
In <option>--start</option> mode, use the existing logical replication slot named
|
2014-10-06 12:11:52 +02:00
|
|
|
<replaceable>slot_name</replaceable>. In <option>--create-slot</option>
|
|
|
|
mode, create the slot with this name. In <option>--drop-slot</option>
|
|
|
|
mode, delete the slot with this name.
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2021-06-30 05:15:47 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-t</option></term>
|
|
|
|
<term><option>--two-phase</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Enables two-phase decoding. This option should only be specified with
|
|
|
|
<option>--create-slot</option>
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2014-03-18 18:20:01 +01:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><option>-v</option></term>
|
|
|
|
<term><option>--verbose</option></term>
|
2014-10-18 15:10:12 +02:00
|
|
|
<listitem>
|
2014-03-18 18:20:01 +01:00
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
Enables verbose mode.
|
2014-03-18 18:20:01 +01:00
|
|
|
</para>
|
2014-10-18 15:10:12 +02:00
|
|
|
</listitem>
|
2014-03-18 18:20:01 +01:00
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2014-10-18 15:10:12 +02:00
|
|
|
The following command-line options control the database connection parameters.
|
2015-09-11 03:22:21 +02:00
|
|
|
|
2014-03-18 18:20:01 +01:00
|
|
|
<variablelist>
|
2014-10-18 15:10:12 +02:00
|
|
|
<varlistentry>
|
2020-10-03 04:19:31 +02:00
|
|
|
<term><option>-d <replaceable>dbname</replaceable></option></term>
|
|
|
|
<term><option>--dbname=<replaceable>dbname</replaceable></option></term>
|
2014-10-18 15:10:12 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2020-10-03 04:19:31 +02:00
|
|
|
The database to connect to. See the description
|
|
|
|
of the actions for what this means in detail.
|
|
|
|
The <replaceable>dbname</replaceable> can be a <link
|
|
|
|
linkend="libpq-connstring">connection string</link>. If so,
|
|
|
|
connection string parameters will override any conflicting
|
|
|
|
command line options. Defaults to the user name.
|
2014-10-18 15:10:12 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2014-03-18 18:20:01 +01:00
|
|
|
|
2014-10-18 15:10:12 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><option>-h <replaceable>hostname-or-ip</replaceable></option></term>
|
2014-10-27 13:53:16 +01:00
|
|
|
<term><option>--host=<replaceable>hostname-or-ip</replaceable></option></term>
|
2014-03-18 18:20:01 +01:00
|
|
|
<listitem>
|
2014-10-18 15:10:12 +02:00
|
|
|
<para>
|
|
|
|
Specifies the host name of the machine on which the server is
|
|
|
|
running. If the value begins with a slash, it is used as the
|
|
|
|
directory for the Unix domain socket. The default is taken
|
|
|
|
from the <envar>PGHOST</envar> environment variable, if set,
|
|
|
|
else a Unix domain socket connection is attempted.
|
|
|
|
</para>
|
2014-03-18 18:20:01 +01:00
|
|
|
</listitem>
|
2014-10-18 15:10:12 +02:00
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><option>-p <replaceable>port</replaceable></option></term>
|
2014-10-27 13:53:16 +01:00
|
|
|
<term><option>--port=<replaceable>port</replaceable></option></term>
|
2014-10-18 15:10:12 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Specifies the TCP port or local Unix domain socket file
|
|
|
|
extension on which the server is listening for connections.
|
|
|
|
Defaults to the <envar>PGPORT</envar> environment variable, if
|
|
|
|
set, or a compiled-in default.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><option>-U <replaceable>user</replaceable></option></term>
|
2014-10-27 13:53:16 +01:00
|
|
|
<term><option>--username=<replaceable>user</replaceable></option></term>
|
2014-10-18 15:10:12 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2015-09-11 03:22:21 +02:00
|
|
|
User name to connect as. Defaults to current operating system user
|
2014-10-18 15:10:12 +02:00
|
|
|
name.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><option>-w</option></term>
|
|
|
|
<term><option>--no-password</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Never issue a password prompt. If the server requires
|
|
|
|
password authentication and a password is not available by
|
|
|
|
other means such as a <filename>.pgpass</filename> file, the
|
|
|
|
connection attempt will fail. This option can be useful in
|
|
|
|
batch jobs and scripts where no user is present to enter a
|
|
|
|
password.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><option>-W</option></term>
|
|
|
|
<term><option>--password</option></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Force <application>pg_recvlogical</application> to prompt for a
|
|
|
|
password before connecting to a database.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
This option is never essential, since
|
|
|
|
<application>pg_recvlogical</application> will automatically prompt
|
|
|
|
for a password if the server demands password authentication.
|
|
|
|
However, <application>pg_recvlogical</application> will waste a
|
|
|
|
connection attempt finding out that the server wants a password.
|
2017-10-09 03:44:17 +02:00
|
|
|
In some cases it is worth typing <option>-W</option> to avoid the extra
|
2014-10-18 15:10:12 +02:00
|
|
|
connection attempt.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
2014-03-18 18:20:01 +01:00
|
|
|
</varlistentry>
|
2014-10-18 15:10:12 +02:00
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The following additional options are available:
|
2014-03-18 18:20:01 +01:00
|
|
|
|
2014-10-18 15:10:12 +02:00
|
|
|
<variablelist>
|
2014-03-18 18:20:01 +01:00
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><option>-V</option></term>
|
|
|
|
<term><option>--version</option></term>
|
2014-03-18 18:20:01 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Print the <application>pg_recvlogical</application> version and exit.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
2017-10-09 03:44:17 +02:00
|
|
|
<term><option>-?</option></term>
|
|
|
|
<term><option>--help</option></term>
|
2014-03-18 18:20:01 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Show help about <application>pg_recvlogical</application> command line
|
|
|
|
arguments, and exit.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
</refsect1>
|
2014-10-18 15:10:12 +02:00
|
|
|
|
2022-09-14 16:32:24 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Exit Status</title>
|
|
|
|
<para>
|
|
|
|
<application>pg_recvlogical</application> will exit with status 0 when
|
|
|
|
terminated by the <systemitem>SIGINT</systemitem> or
|
|
|
|
<systemitem>SIGTERM</systemitem> signal. (That is the
|
|
|
|
normal way to end it. Hence it is not an error.) For fatal errors or
|
|
|
|
other signals, the exit status will be nonzero.
|
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
2014-10-18 15:10:12 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Environment</title>
|
|
|
|
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
This utility, like most other <productname>PostgreSQL</productname> utilities,
|
|
|
|
uses the environment variables supported by <application>libpq</application>
|
2017-11-23 15:39:47 +01:00
|
|
|
(see <xref linkend="libpq-envars"/>).
|
2014-10-18 15:10:12 +02:00
|
|
|
</para>
|
Unified logging system for command-line programs
This unifies the various ad hoc logging (message printing, error
printing) systems used throughout the command-line programs.
Features:
- Program name is automatically prefixed.
- Message string does not end with newline. This removes a common
source of inconsistencies and omissions.
- Additionally, a final newline is automatically stripped, simplifying
use of PQerrorMessage() etc., another common source of mistakes.
- I converted error message strings to use %m where possible.
- As a result of the above several points, more translatable message
strings can be shared between different components and between
frontends and backend, without gratuitous punctuation or whitespace
differences.
- There is support for setting a "log level". This is not meant to be
user-facing, but can be used internally to implement debug or
verbose modes.
- Lazy argument evaluation, so no significant overhead if logging at
some level is disabled.
- Some color in the messages, similar to gcc and clang. Set
PG_COLOR=auto to try it out. Some colors are predefined, but can be
customized by setting PG_COLORS.
- Common files (common/, fe_utils/, etc.) can handle logging much more
simply by just using one API without worrying too much about the
context of the calling program, requiring callbacks, or having to
pass "progname" around everywhere.
- Some programs called setvbuf() to make sure that stderr is
unbuffered, even on Windows. But not all programs did that. This
is now done centrally.
Soft goals:
- Reduces vertical space use and visual complexity of error reporting
in the source code.
- Encourages more deliberate classification of messages. For example,
in some cases it wasn't clear without analyzing the surrounding code
whether a message was meant as an error or just an info.
- Concepts and terms are vaguely aligned with popular logging
frameworks such as log4j and Python logging.
This is all just about printing stuff out. Nothing affects program
flow (e.g., fatal exits). The uses are just too varied to do that.
Some existing code had wrappers that do some kind of print-and-exit,
and I adapted those.
I tried to keep the output mostly the same, but there is a lot of
historical baggage to unwind and special cases to consider, and I
might not always have succeeded. One significant change is that
pg_rewind used to write all error messages to stdout. That is now
changed to stderr.
Reviewed-by: Donald Dong <xdong@csumb.edu>
Reviewed-by: Arthur Zakirov <a.zakirov@postgrespro.ru>
Discussion: https://www.postgresql.org/message-id/flat/6a609b43-4f57-7348-6480-bd022f924310@2ndquadrant.com
2019-04-01 14:24:37 +02:00
|
|
|
|
|
|
|
<para>
|
|
|
|
The environment variable <envar>PG_COLOR</envar> specifies whether to use
|
2020-03-09 02:53:22 +01:00
|
|
|
color in diagnostic messages. Possible values are
|
|
|
|
<literal>always</literal>, <literal>auto</literal> and
|
Unified logging system for command-line programs
This unifies the various ad hoc logging (message printing, error
printing) systems used throughout the command-line programs.
Features:
- Program name is automatically prefixed.
- Message string does not end with newline. This removes a common
source of inconsistencies and omissions.
- Additionally, a final newline is automatically stripped, simplifying
use of PQerrorMessage() etc., another common source of mistakes.
- I converted error message strings to use %m where possible.
- As a result of the above several points, more translatable message
strings can be shared between different components and between
frontends and backend, without gratuitous punctuation or whitespace
differences.
- There is support for setting a "log level". This is not meant to be
user-facing, but can be used internally to implement debug or
verbose modes.
- Lazy argument evaluation, so no significant overhead if logging at
some level is disabled.
- Some color in the messages, similar to gcc and clang. Set
PG_COLOR=auto to try it out. Some colors are predefined, but can be
customized by setting PG_COLORS.
- Common files (common/, fe_utils/, etc.) can handle logging much more
simply by just using one API without worrying too much about the
context of the calling program, requiring callbacks, or having to
pass "progname" around everywhere.
- Some programs called setvbuf() to make sure that stderr is
unbuffered, even on Windows. But not all programs did that. This
is now done centrally.
Soft goals:
- Reduces vertical space use and visual complexity of error reporting
in the source code.
- Encourages more deliberate classification of messages. For example,
in some cases it wasn't clear without analyzing the surrounding code
whether a message was meant as an error or just an info.
- Concepts and terms are vaguely aligned with popular logging
frameworks such as log4j and Python logging.
This is all just about printing stuff out. Nothing affects program
flow (e.g., fatal exits). The uses are just too varied to do that.
Some existing code had wrappers that do some kind of print-and-exit,
and I adapted those.
I tried to keep the output mostly the same, but there is a lot of
historical baggage to unwind and special cases to consider, and I
might not always have succeeded. One significant change is that
pg_rewind used to write all error messages to stdout. That is now
changed to stderr.
Reviewed-by: Donald Dong <xdong@csumb.edu>
Reviewed-by: Arthur Zakirov <a.zakirov@postgrespro.ru>
Discussion: https://www.postgresql.org/message-id/flat/6a609b43-4f57-7348-6480-bd022f924310@2ndquadrant.com
2019-04-01 14:24:37 +02:00
|
|
|
<literal>never</literal>.
|
|
|
|
</para>
|
2014-10-18 15:10:12 +02:00
|
|
|
</refsect1>
|
|
|
|
|
2018-04-07 23:45:39 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Notes</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
<application>pg_recvlogical</application> will preserve group permissions on
|
|
|
|
the received WAL files if group permissions are enabled on the source
|
|
|
|
cluster.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
</refsect1>
|
|
|
|
|
2014-10-31 03:52:21 +01:00
|
|
|
<refsect1>
|
|
|
|
<title>Examples</title>
|
|
|
|
|
|
|
|
<para>
|
2017-11-23 15:39:47 +01:00
|
|
|
See <xref linkend="logicaldecoding-example"/> for an example.
|
2014-10-31 03:52:21 +01:00
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
2014-10-18 15:10:12 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>See Also</title>
|
|
|
|
|
|
|
|
<simplelist type="inline">
|
2017-11-23 15:39:47 +01:00
|
|
|
<member><xref linkend="app-pgreceivewal"/></member>
|
2014-10-18 15:10:12 +02:00
|
|
|
</simplelist>
|
|
|
|
</refsect1>
|
2014-03-18 18:20:01 +01:00
|
|
|
</refentry>
|