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.

Available12 minDesktop

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. 1

    Create the connection

    Open Library, choose Create connection, and select PostgreSQL and a supported Connection method tab.

  2. 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.
    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. 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. 4

    Select a scope

    Select the database / schema scope that should be attached to the new tab.

  5. 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.
    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. 6

    Inspect the result

    Inspect Results, Messages, History, and Details; dock the panel on the bottom or right as needed.

  7. 7

    Export when needed

    Export only the required rows after reviewing format, destination, and redaction options.

  8. 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

FieldRequiredPurposeSafe example
NameYesA clear profile name, without credentials.PostgreSQL development
Connection methodYesChoose a supported tab. The fields below apply only to the selected method and deployment.Connection fields / Connection string
EnvironmentNoAttach the intended variable and safety context.Local development
Read-only connectionNoEnable for initial exploration. This does not make pre-release software safe for production workloads.Enabled
Host / PortNoEndpoint 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 scopeNoInitial scope for browsing, where supported.catalog
Complete connection stringYesRequired 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
UsernameNoAuthentication identity for the selected method.catalog_reader
PasswordNoRequired 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
TransportNoGeneral. 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 directoryNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Application nameNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Search pathNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Target sessionNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.any / read-write / read-only
Use TLSNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Verify server certificateNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
CA certificateNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Client certificateNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Client keyNoTLS & certificates. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Connect timeout (ms)NoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Statement timeout (ms)NoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Lock timeout (ms)NoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Idle transaction timeout (ms)NoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default

Run the sample query

PostgreSQL read-only example
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.
Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action.
Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action. Open full size

Capabilities and availability

CapabilityStatusNotes
Native explorerAvailableBrowse databases, schemas, tables, views, columns, indexes, routines, extensions, roles, role memberships, grants, and default privileges.
Read queriesAvailableRun raw PostgreSQL SQL with metadata-aware snippets for pg_catalog, routines, sessions, locks, search paths, and mixed-case identifier quoting.
Inline editingGuardedRequires key evidence, a writable profile, and environment confirmation.
Diagnostics / administrationGuardedPreview VACUUM, ANALYZE, REINDEX, role grant/revoke, extension update/drop, parameterized routine execution, and backend cancel or terminate actions.
Import / export / transferGuardedAvailability follows the authoritative runtime transfer manifest and shows a disabled reason when execution is not implemented.

Safety and limitations

Troubleshooting

SymptomResolution
Test connection fails or times outVerify 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 disabledConfirm the selected database / schema, refresh the branch, and grant the minimum metadata permissions described in the connection warning.
Run, edit, admin, or transfer is disabledRead 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 columnsReplace the example names with objects from your PostgreSQL datastore, confirm the selected database / schema, and keep the query bounded while you validate the result.