> ## Documentation Index > Fetch the complete documentation index at: https://vexidata.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # PostgreSQL > Connect your PostgreSQL database to VexiData. If you're using a managed PostgreSQL service, check our provider-specific guides for step-by-step instructions tailored to your platform: ## Prerequisites * A PostgreSQL database (version 12 or later recommended) that is accessible over the network * The database host, port, name, username, and password * A [VexiData](https://vexidata.com) account ## Connect PostgreSQL to VexiData You need five pieces of information to connect. If you set up PostgreSQL yourself, you'll already know these. If someone else manages the database, ask your database administrator. | Parameter | Description | Default | | ------------ | ---------------------------------------------------- | ----------- | | **Host** | The hostname or IP address of your PostgreSQL server | `localhost` | | **Port** | The port PostgreSQL is listening on | `5432` | | **Database** | The name of the database you want to query | `postgres` | | **Username** | A PostgreSQL user with access to the database | `postgres` | | **Password** | The password for that user | — | If your PostgreSQL server is behind a firewall or only accepts connections from specific IPs, add VexiData's IP addresses: * `46.101.71.122` **Common places to configure this:** * **Cloud VMs** (AWS EC2, DigitalOcean Droplets, GCP Compute) — Security Groups or firewall rules * **Self-hosted servers** — `pg_hba.conf` and/or your OS firewall (e.g., `ufw`, `iptables`) * **Managed databases** — See the provider-specific guides linked above If your database is only accessible from `localhost` or a private network, you'll need to either expose it to the internet or set up an SSH tunnel. VexiData requires a direct TCP connection to your database. By default, PostgreSQL only listens on `localhost`. If your database is on a remote server, make sure it's configured to accept external connections: 1. In `postgresql.conf`, set: ``` listen_addresses = '*' ``` 2. In `pg_hba.conf`, add a line allowing VexiData's IPs (or all IPs if behind a firewall): ``` host all all 46.101.71.122/32 scram-sha-256 ``` 3. Restart PostgreSQL for changes to take effect. Managed database services (Supabase, Neon, RDS, etc.) handle this automatically. You only need this step for self-hosted PostgreSQL. 1. Go to [Data Sources](https://vexidata.com/data-sources) in VexiData 2. Click **PostgreSQL** to open the connection form 3. Fill in the details: | Field | Value | | ---------------- | -------------------------------------------------------------------- | | **Display Name** | A name to identify this connection (e.g., "Production DB") | | **Host** | Your server's hostname or IP address | | **Port** | `5432` (or your custom port) | | **Database** | Your database name | | **Schema** | `public` (default — change if your tables are in a different schema) | | **Username** | Your PostgreSQL username | | **Password** | Your PostgreSQL password | Click **Test & Save Connection**. VexiData will verify it can reach your database. Once connected, your schema will be analyzed automatically. ## Creating a read-only user (recommended) For security, we recommend connecting VexiData with a dedicated read-only user instead of your admin or application user. This ensures VexiData can only read data, never modify it. ```sql theme={null} -- Create the user CREATE USER vexidata WITH PASSWORD 'your-secure-password'; -- Grant connect access to the database GRANT CONNECT ON DATABASE your_database TO vexidata; -- Grant read access to the public schema GRANT USAGE ON SCHEMA public TO vexidata; GRANT SELECT ON ALL TABLES IN SCHEMA public TO vexidata; -- Ensure future tables are also readable ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO vexidata; ``` If your tables are in a **custom schema**, replace `public` with your schema name in the commands above. ## Troubleshooting This means VexiData can't reach your server. Check: * Your firewall allows inbound connections on the PostgreSQL port from VexiData's IPs * `listen_addresses` in `postgresql.conf` is set to `'*'` (not `'localhost'`) * Your server has a public IP or hostname that resolves correctly * If on a cloud VM, the Security Group / firewall rules allow traffic on port `5432` * Verify the username and password are correct * Check `pg_hba.conf` allows the authentication method you're using (e.g., `scram-sha-256` or `md5`) for remote connections * Some setups use `peer` or `ident` authentication which only works for local connections — remote connections need password-based auth * PostgreSQL is case-sensitive for database names. Make sure the name matches exactly (e.g., `MyApp` is different from `myapp`) * Run `\l` in `psql` to list all available databases * Confirm your tables are in the `public` schema. If they're in a custom schema (e.g., `app` or `api`), update the **Schema** field in VexiData * Check that your user has `SELECT` permissions: `GRANT SELECT ON ALL TABLES IN SCHEMA public TO your_user;` * If your server requires SSL, VexiData will attempt SSL automatically * For self-hosted servers, ensure your PostgreSQL SSL certificates are properly configured * Check that `ssl = on` is set in `postgresql.conf` if you require encrypted connections