SQL and relational
PostgreSQL
PostgreSQL gets a typed SQL workbench with rich catalog views, live read execution, primary-key row evidence, and guarded operational previews.
Prerequisites
- Install the current DataPad++ desktop pre-release on Windows, macOS, or Linux.
- Have the endpoint, database file, or cloud account details for a PostgreSQL datastore you are authorized to use. Start with least-privileged, read-only access.
- Keep an independent backup before enabling edits, administration, restore, or transfer execution.
Connect and run a safe query
- 1
Create the connection
Open Library, choose Create connection, and select PostgreSQL and a supported Connection method tab.
- 2
Test and save
Complete the applicable fields and enable Read-only connection. Test connection when available; new local files and pending secondary credential changes must be saved first. Review runtime limitations and warnings.

PostgreSQL connection setup. The PostgreSQL connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving. Open full size - 3
Open the native explorer
Use Save Connection, or Create Database and Save Connection for a new local file, then open the PostgreSQL Explorer where supported.
- 4
Select a scope
Select the database / schema scope that should be attached to the new tab.
- 5
Run a bounded read
Open a query tab, paste the bounded read-only sample below, and choose Run or press Ctrl/Cmd+Enter.

PostgreSQL native workflow. A representative PostgreSQL explorer and bounded read-only workflow. Replace the example objects with names from your datastore. Open full size - 6
Inspect the result
Inspect Results, Messages, History, and Details; dock the panel on the bottom or right as needed.
- 7
Export when needed
Export only the required rows after reviewing format, destination, and redaction options.
- 8
Open diagnostics or transfers
Open Diagnostics or Transfers from the drawer/status bar and treat disabled reasons as capability boundaries, not transient errors.
Connection fields
| Field | Required | Purpose | Safe example |
|---|---|---|---|
| Name | Yes | A clear profile name, without credentials. | PostgreSQL development |
| Connection method | Yes | Choose a supported tab. The fields below apply only to the selected method and deployment. | Connection fields / Connection string |
| Environment | No | Attach the intended variable and safety context. | Local development |
| Read-only connection | No | Enable for initial exploration. This does not make pre-release software safe for production workloads. | Enabled |
| Host / Port | No | Endpoint for a fields-based connection. Follow the selected deployment and runtime limitations; MongoDB SRV does not use an explicit port. | localhost / engine default |
| Database / default scope | No | Initial scope for browsing, where supported. | catalog |
| Complete connection string | Yes | Required in Connection string mode only. Saved unchanged as one vault secret with Save Connection. Blank keeps an existing stored value. | Paste your complete provider string; do not share it |
| Username | No | Authentication identity for the selected method. | catalog_reader |
| Password | No | Required only when the chosen authentication needs it. Save Connection stores changes; blank preserves an existing value, and Reveal… explicitly discloses it. | Stored in the desktop OS vault |
| Transport | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | tcp / unix-socket / cloud-sql-proxy / managed-postgres |
| Unix socket directory | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Application name | No | Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Search path | No | Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Target session | No | Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | any / read-write / read-only |
| Use TLS | No | TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Verify server certificate | No | TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| CA certificate | No | TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Client certificate | No | TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Client key | No | TLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Connect timeout (ms) | No | Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Statement timeout (ms) | No | Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Lock timeout (ms) | No | Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Idle transaction timeout (ms) | No | Advanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
Run the sample query
SELECT id, name, status
FROM public.customers
ORDER BY id
LIMIT 25;Explore and inspect
- Browse databases, schemas, tables, views, columns, indexes, routines, extensions, roles, role memberships, grants, and default privileges.
- Use object actions to open scoped SELECTs, routine-call previews, extension reviews, grants, and maintenance plans.
- Inspect table grids with sticky headers, row selection, messages, details, and rendered plan dashboards.
- Live row edits require table and primary-key identity and include before/after RETURNING evidence where supported.
Diagnose, administer, and transfer
- Review pg_stat_activity, pg_locks, pg_stat_user_tables, relation/vacuum/index posture, wait or blocking signals, and optional pg_stat_statements top-query data.
- Preview VACUUM, ANALYZE, REINDEX, role grant/revoke, extension update/drop, parameterized routine execution, and backend cancel or terminate actions.
- Full pg_dump and pg_restore backup compatibility is unavailable because DataPad++ does not invoke external vendor executables.
- Import — Live. PostgreSQL streams native text, CSV, and binary data through driver-level COPY. JSON and NDJSON remain portable conversions. Formats: PostgreSQL COPY text (native), PostgreSQL COPY CSV (native), PostgreSQL binary COPY (native), JSON (portable), NDJSON (portable). Destinations: local file.
- Export — Live. PostgreSQL streams native text, CSV, and binary data through driver-level COPY. JSON and NDJSON remain portable conversions. Formats: PostgreSQL COPY text (native), PostgreSQL COPY CSV (native), PostgreSQL binary COPY (native), JSON (portable), NDJSON (portable). Destinations: local file.
- Backup — Unavailable. This datastore has no supported in-process or server API for a full native backup artifact. Formats: Native managed backup (native). Destinations: cloud uri, server path. Full PostgreSQL backup and restore require excluded vendor tooling or storage-backend access.
- Restore — Unavailable. This datastore has no supported in-process or server API for a full native backup artifact. Formats: Native managed backup (native). Destinations: cloud uri, server path. Full PostgreSQL backup and restore require excluded vendor tooling or storage-backend access.

Capabilities and availability
| Capability | Status | Notes |
|---|---|---|
| Native explorer | Available | Browse databases, schemas, tables, views, columns, indexes, routines, extensions, roles, role memberships, grants, and default privileges. |
| Read queries | Available | Run raw PostgreSQL SQL with metadata-aware snippets for pg_catalog, routines, sessions, locks, search paths, and mixed-case identifier quoting. |
| Inline editing | Guarded | Requires key evidence, a writable profile, and environment confirmation. |
| Diagnostics / administration | Guarded | Preview VACUUM, ANALYZE, REINDEX, role grant/revoke, extension update/drop, parameterized routine execution, and backend cancel or terminate actions. |
| Import / export / transfer | Guarded | Availability follows the authoritative runtime transfer manifest and shows a disabled reason when execution is not implemented. |
Safety and limitations
Troubleshooting
| Symptom | Resolution |
|---|---|
| Test connection fails or times out | Verify endpoint, port, TLS mode, proxy settings, service health, firewall rules, and network access. Keep the profile unsaved until the test explains the failure. |
| Explorer branches are empty or disabled | Confirm the selected database / schema, refresh the branch, and grant the minimum metadata permissions described in the connection warning. |
| Run, edit, admin, or transfer is disabled | Read the visible disabled reason. Select a compatible target, turn off read-only only when authorized, or use the documented preview/export fallback. |
| The sample query fails or returns different columns | Replace the example names with objects from your PostgreSQL datastore, confirm the selected database / schema, and keep the query bounded while you validate the result. |