---
name: "SLONIK_ADMIN_CONNINFO"
section: "7"
platform: "linux"
package: "slony1-2-doc"
version: "2.2.11-6"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/SLONIK_ADMIN_CONNINFO"
---

# SLONIK\_ADMIN\_CONNINFO(7)

preamble - identifying PostgreSQL database

## NAME

ADMIN CONNINFO - preamble - identifying PostgreSQL database

## SYNOPSIS

FC**NODE ival ADMIN CONNINFO = 'DSN';**F\[0\]  \[ *ival;*\] \[ *'conninfo'*\]

## 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 FC**PQconnectdb()**F\[0\] libpq function.

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 authentication schemes like ‘trust’. Alternatively, libpq can read passwords from FC*.pgpass* F\[0\].

**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 **SLONIK 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 configuration change.

## EXAMPLE

```
FC     NODE 1 ADMIN CONNINFO = 'dbname=testdb host=server1 user=slony';
    F[0]
```

## VERSION INFORMATION

This command was introduced in Slony-I 1.0