Provided by:
slony1-doc_1.2.15-1_all 
NAME
ADMIN CONNINFO - preamble - identifying PostgreSQL database
SYNOPSIS
NODE ival ADMIN CONNINFO = DSN ; [ ival;] [ ’conninfo’]
DESCRIPTION
Describes how the slonik utility can reach a nodes database in the
cluster from where it is run (likely the DBA’s workstation). The con‐
ninfo string is the string agrument given to the PQconnectdb() libpq
function. The user used to connect must be the special replication su‐
peruser, as some of the actions performed later may include operations
that are strictly reserved for database superusers by PostgreSQL.
The slonik utility will not try to connect to a given database unless
some subsequent command requires the connection.
Note
As mentioned in the original documents, Slony-I is designed as
an enterprise replication system for data centers. It has been
assumed throughout the entire development that the database
servers and administrative workstations involved in replication
and/or setup and configuration activities can use simple authen‐
tication schemes like ‘trust’. Alternatively, libpq can read
passwords from .pgpass .
Note
If you need to change the DSN information for a node, as would
happen if the IP address for a host were to change, you must
submit the new information using the STORE PATH(7) command, and
that configuration will be propagated. Existing slon processes
may need to be restarted in order to become aware of the config‐
uration change.
For more details on the distinction between this and STORE PATH(7), see
“ Slony-I Path Communications” [not available as a man page].
EXAMPLE
NODE 1 ADMIN CONNINFO = ’dbname=testdb host=server1 user=slony’;
This command was introduced in Slony-I 1.0
17 November 2008 ADMIN CONNINFO(7)