Postgres

Connect Postgres to query your databases data in Queringo.

At a glance

Setup

1. Open Connect source

   In the app, go to Data sources and choose Connect source. Open the Databases tab and select Postgres.

2. Enter connection details

   Provide the host, port, database name, and a read-only user and password. The default port is 5432. Enable SSL/TLS if your database requires it, or configure an SSH tunnel for a private network.

3. Save the connection

   Queringo tests the connection before saving, then discovers the schema. PII is flagged and masked by default during discovery.

Where to find these in your provider

1. Connect to your Postgres server as a superuser (psql, pgAdmin, or your cloud's console).
2. Create a read-only role for Queringo, for example: CREATE ROLE queringo LOGIN PASSWORD '…';
3. Grant read access on the schemas you want exposed, for example: GRANT USAGE ON SCHEMA public TO queringo; GRANT SELECT ON ALL TABLES IN SCHEMA public TO queringo;
4. Make sure Queringo's outbound address can reach your host on port 5432 (or set up an SSH tunnel).

Test the connection

Queringo runs a connection test as part of saving. If it fails, the error message indicates what to check (credentials, network reachability, or scope). From Data sources, you can re-run Test connection on the source row any time, for example after rotating a secret or changing network rules.

Edit or rotate

To change connection details (host, port, or database), open the source from Data sources and edit it. To swap only the secret (password, key file, or token), use Rotate credentials so existing dashboards and alerts keep working. See Rotating credentials.

Reference

• Postgres: managing roles and privileges

Suggest a different connector

Don't see what you need? In the Connect a data source picker, choose Request it. Queringo bundles votes from every workspace asking for the same one and prioritizes accordingly.

Related connectors

• MongoDB
• MySQL
• SQL Server

What's next

For the category overview and shared options, see Databases. To keep sources healthy, see Managing sources.