PostgreSQL Connection String Workbench

How to use PostgreSQL Connection String Workbench

Inspect or convert a bounded libpq connection URI or keyword/value string, including multiple hosts and explicit parameter overrides. Review decoded fields, preserved empty values and host alignment. Start with a redacted report, then explicitly choose whether a local conversion should contain the supplied secrets.

1. Provide connection string: selected libpq 18 profile.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• 32,768 UTF-8 bytes, 100 parameter occurrences, 8,192 characters per decoded value and 20 host alternatives. A fixed documented subset of libpq 18 keywords is accepted; unsupported options, service-file resolution and nested dbname expansion are refused or not interpreted.
• Selected well-formed UTF-8 profile. Keyword/value parsing supports ASCII whitespace, single quotes and backslash escaping; URI parsing supports postgres/postgresql, bracketed hosts, percent encoding, multiple hosts and last occurrence wins. Plus remains a literal plus; query values containing = must encode it. Raw URI whitespace and fragments are refused.
• This parser lists supplied parameters only. It does not validate every option value, hostname, address, port, TLS policy or authentication behavior, supply environment/build defaults, open files or attempt a connection. Host array mismatches are explicit diagnostics.
• Redacted mode removes password and sslpassword from every result field. Conversion including secrets is an explicit choice and places those values in copied/downloaded output; use original test inputs or keys you are authorized to handle.
• The separate JSON report is limited to 500,000 characters, including formatting; reduce the source if the report exceeds that bound.
• Inputs are processed on this device and are not automatically saved or uploaded.