'\" -*- coding: us-ascii -*-
.if \n(.g .ds T< \\FC
.if \n(.g .ds T> \\F[\n[.fam]]
.de URL
\\$2 \(la\\$1\(ra\\$3
..
.if \n(.g .mso www.tmac
.TH "SLONIK ADMIN CONNINFO" 7 "24 July 2014" "" "Slony-I 2.2.3 Documentation"
.SH NAME
ADMIN CONNINFO \- preamble - identifying PostgreSQL database 
.SH SYNOPSIS
'nh
.fi
.ad l
\fBNODE ival ADMIN CONNINFO = 'DSN';\fR \kx
.if (\nx>(\n(.l/2)) .nr x (\n(.l/5)
'in \n(.iu+\nxu
[\fI ival;\fR] [\fI 'conninfo'\fR]
'in \n(.iu-\nxu
.ad b
'hy
.SH DESCRIPTION
Describes how the slonik utility can
reach a node's database in the cluster from where it is run
(likely the DBA's workstation). The conninfo string is the string
agrument given to the \*(T<\fBPQconnectdb()\fR\*(T> libpq
function. 
.PP
The slonik utility will not try to
connect to a given database unless some subsequent command
requires the connection.
.RS 
\fBNote\fR
.PP
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 authentication
schemes like \(oqtrust\(cq. Alternatively, libpq can read
passwords from \*(T<\fI.pgpass \fR\*(T>.
.RE
.RS 
\fBNote\fR
.PP
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 \fBSLONIK STORE
PATH\fR(7) command, and that configuration will be
propagated. Existing slon processes
may need to be restarted in order to become aware of the
configuration change.
.RE
.SH EXAMPLE
.nf
\*(T<     NODE 1 ADMIN CONNINFO = 'dbname=testdb host=server1 user=slony';
    \*(T>
.fi
.SH "VERSION INFORMATION "
This command was introduced in Slony-I 1.0