PostgreSQL

pg_recvlogical — control PostgreSQL logical decoding streams

pg_recvlogical [`option`…​]

pg_recvlogical controls logical decoding replication slots and streams data from such replication slots.

It creates a replication-mode connection, so it is subject to the same constraints as pg_receivewal, plus those for logical replication (see Chapter 49).

pg_recvlogical has no equivalent to the logical decoding 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 pg_logical_slot_peek_changes.

In the absence of fatal errors, pg_recvlogical will run until terminated by the SIGINT ([.keycap]]Control+C) or SIGTERM signal.

At least one of the following options must be specified to select an action:

--create-slot and --start can be specified together. --drop-slot cannot be combined with another action.

The following command-line options control the location and format of the output and other replication behavior:

-E +`_`+lsn`_
#[.term]--endpos=lsn:: In `--start mode, automatically stop replication and exit with normal exit status 0 when receiving reaches the specified LSN. If specified when not in --start mode, an error is raised.
If there’s a record with LSN exactly equal to `lsn, the record will be output.
The `--endpos 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. [.term]-f +`_`+filename`_
[.term]--file=filename:: Write received and decoded transaction data into this file. Use `- for [.systemitem]#stdout. -F +`_`+interval_seconds`_
#[.term]--fsync-interval=interval_seconds:: Specifies how often pg_recvlogical should issue `fsync() calls to ensure the output file is safely flushed to disk.
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.
Specifying an interval of 0 disables issuing fsync() calls altogether, while still reporting progress to the server. In this case, data could be lost in the event of a crash. [.term]-I +`_`+lsn`_
[.term]--startpos=lsn:: In `--start mode, start replication from the given LSN. For details on the effect of this, see the documentation in Chapter 49 and Section 55.4. Ignored in other modes. [.term]--if-not-exists:: Do not error out when --create-slot is specified and a slot with the specified name already exists. [.term]-n
[.term]--no-loop:: When the connection to the server is lost, do not retry in a loop, just exit. [.term]-o +`_`+name`[=value]`
[.term]--option=`name[=value]:: Pass the option _name to the output plugin with, if specified, the option value value. Which options exist and their effects depends on the used output plugin. [.term]-P +`_`+plugin_
[.term]--plugin=plugin:: When creating a slot, use the specified logical decoding output plugin. See Chapter 49. This option has no effect if the slot already exists. [.term]-s +`_`+interval_seconds_
[.term]--status-interval=interval_seconds:: This option has the same effect as the option of the same name in [.refentrytitle#pg_receivewal]. See the description there. -S +`_`+slot_name_
#[.term]--slot=slot_name:: In `--start mode, use the existing logical replication slot named `slot_name. In `--create-slot mode, create the slot with this name. In --drop-slot mode, delete the slot with this name. [.term]-t
[.term]--two-phase:: Enables decoding of prepared transactions. This option may only be specified with --create-slot [.term]-v
[.term]--verbose#:: Enables verbose mode.

The following command-line options control the database connection parameters.

-d +`_`+dbname`_
#[.term]--dbname=dbname:: The database to connect to. See the description of the actions for what this means in detail. The dbname can be a connection string. If so, connection string parameters will override any conflicting command line options. Defaults to the user name. [.term]-h +`_`+hostname-or-ip_
[.term]--host=hostname-or-ip:: 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 `PGHOST environment variable, if set, else a Unix domain socket connection is attempted. [.term]-p +`_`+port`_
[.term]--port=port:: Specifies the TCP port or local Unix domain socket file extension on which the server is listening for connections. Defaults to the `PGPORT environment variable, if set, or a compiled-in default. [.term]-U +`_`+user`_
[.term]--username=user:: User name to connect as. Defaults to current operating system user name. [.term]-w`
[.term]--no-password:: Never issue a password prompt. If the server requires password authentication and a password is not available by other means such as a .pgpass 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. [.term]-W
[.term]--password#:: Force pg_recvlogical to prompt for a password before connecting to a database.
This option is never essential, since pg_recvlogical will automatically prompt for a password if the server demands password authentication. However, pg_recvlogical will waste a connection attempt finding out that the server wants a password. In some cases it is worth typing -W to avoid the extra connection attempt.

The following additional options are available:

-V
#[.term]--version:: Print the pg_recvlogical version and exit. [.term]-?
[.term]--help#:: Show help about pg_recvlogical command line arguments, and exit.

pg_recvlogical will exit with status 0 when terminated by the SIGINT or SIGTERM 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.

This utility, like most other PostgreSQL utilities, uses the environment variables supported by libpq (see Section 34.15).

The environment variable PG_COLOR specifies whether to use color in diagnostic messages. Possible values are always, auto and never.

pg_recvlogical will preserve group permissions on the received WAL files if group permissions are enabled on the source cluster.

See Section 49.1 for an example.

[.refentrytitle#pg_receivewal]#

If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.

Privacy Policy | Code of Conduct | About PostgreSQL | Contact

Copyright © 1996-2024 The PostgreSQL Global Development Group