Connect to a PostgreSQL for 1C cluster
You can connect to a PostgreSQL for 1C cluster:
- via the psql console client;
- using the pgAdmin graphical database management tool;
- using 1C:Enterprise and other office suites or applications with ODBC or JDBC support;
- using programming code.
Connection with an SSL certificate is unavailable.
When connecting, specify the port and address.
Connection ports
Use these ports to connect to PostgreSQL for 1C:
- 5432 — the port for direct connection to the PostgreSQL for 1C process;
- 6432 — the port for connection to the master node.
Connection addresses
You can select a connection address based on one of the following scenarios:
- connecting to a cluster in a public subnet;
- connecting from a private subnet to a cluster in a private subnet;
- connecting from the Internet to a cluster in a private subnet.
You can view the connection address in the Control Panel.

Connecting to a cluster in a public subnet
If the cluster is in a public subnet, you can connect to the nodes using a DNS address or an IP address from the public subnet.
We recommend connecting via a DNS address. The cluster uses the master discovery mechanism for DNS addresses: the address is linked to the node role, not to the node itself. If the master becomes unavailable, one of the replicas becomes the new master, and the address moves to the new node along with the role.
When connecting via an IP address from a public subnet, the master discovery mechanism is not used. If one of the replicas becomes the new master, the master IP address will change, and the connection via the old IP address will stop working.
Connecting from a private subnet to a cluster in a private subnet
If you are connecting from a private subnet to a cluster in a private subnet, you can use a DNS address or a private IP address.
We recommend connecting via a DNS address. The cluster uses the master discovery mechanism for DNS addresses: the address is linked to the node role, not to the node itself. If the master becomes unavailable, one of the replicas becomes the new master, and the address moves to the new node along with the role.
When connecting via a private IP address, the master discovery mechanism is not used. If one of the replicas becomes the new master, the master IP address will change, and the connection via the old IP address will stop working.
To connect from another private subnet, first connect both private subnets to a cloud router.
Connecting from the Internet to a cluster in a private subnet
If you are connecting to a cluster on a private subnet from the Internet, you can only use a public IP address (Floating IP). The private subnet must meet the requirements. If the subnet does not meet the requirements, prepare it for a public IP address (Floating IP).
The master discovery mechanism is used for public IP addresses (Floating IPs): the address is linked to the node role, not to the node itself. If the master becomes unavailable, one of the replicas becomes the new master, and the address moves to the new node along with the role.
View the connection address
- In the Control Panel, click Products in the top menu and select Managed Databases.
- Open the Active tab.
- Open the database cluster page → Connection tab.
- In the Connection addresses block, view the address.
Connect to a cluster
1C:Enterprise
Bash
To connect a PostgreSQL for 1C database as a 1C infobase, use the following parameters in the infobase addition form in 1C:Enterprise:
- Secure connection — disabled;
- DBMS type — PostgreSQL;
- Database server — node DNS name or public IP address (Floating IP);
- Database name — the name of the created database;
- Database user — the database username;
- User password — password.