ssl_min_protocol_version
Read PG 18 manual ↗Sets the minimum SSL/TLS protocol version to use.
- Type
- enum
- Context
- sighup
- Measured default
- TLSv1.2
- Unit
- —
- Metadata snapshot
- 18
- Allowed values
- TLSv1, TLSv1.1, TLSv1.2, TLSv1.3
Definition PG 18 manual
Sets the minimum SSL/TLS protocol version to use. Valid values are currently: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3. Older versions of the OpenSSL library do not support all values; an error will be raised if an unsupported setting is chosen. Protocol versions before TLS 1.0, namely SSL version 2 and 3, are always disabled.
The default is TLSv1.2, which satisfies industry best practices as of this writing.
This parameter can only be set in the postgresql.conf file or on the server command line.
Measured default history
| Version interval | Default |
|---|---|
| 12 – 12 | TLSv1 |
| 13 – 19 | TLSv1.2 |
Authored guidance from the GUC source snapshot; the version-specific manual above is the definition reference. View source ↗
How it works
ssl_min_protocol_version sets the minimum SSL/TLS protocol version to use. Connections negotiating below the floor are rejected; the upstream default moved from TLSv1 in PostgreSQL 12 to TLSv1.2 in PostgreSQL 13.
ssl_min_protocol_version is a SIGHUP-context setting: a configuration reload activates the new server value without a restart; subsequent operations that consult it use the refreshed value. Existing TLS sessions are not renegotiated.
It participates in the TLS context used for new handshakes. ssl enables transport, pg_hba.conf decides which connection classes require it, and the certificate, key, CA, revocation, protocol, and cipher settings must form one valid policy.
Operational considerations
Editing ssl_min_protocol_version without reloading configuration and verifying the effective value and subsequent behavior.
Updating only one TLS file or policy knob and leaving an invalid chain, unreadable key, or incompatible protocol set.
Assuming a reload renegotiates existing sessions; TLS policy changes affect new handshakes.
Changing ssl_min_protocol_version globally without a rollback plan and a client or operational compatibility test.
Workload guidance
OLAP: Use the same TLS floor for analytical traffic; benchmark only after correctness because bulk transfer may expose CPU cost but is not a reason to accept obsolete protocols.
OLTP: Treat ssl_min_protocol_version as transport-security policy rather than a performance knob. Follow the organization's TLS baseline and test certificate rotation, reload, and every client class.
SMALL: Keep ssl_min_protocol_version simple and secure, using managed certificates and library defaults reviewed for the installed OpenSSL version. Rehearse renewal before expiry.
Version history 2
- PG 12 → 13changed
- PG 11 → 12added
Related entries
Further reading
Definition snapshot: english-manuals:cdc844b54928995abed9ed3d56c… · English manual source