ssl_crl_file
Read PG 18 manual ↗Specifies the name of the file containing the SSL client certificate revocation list (CRL).
- Type
- string
- Context
- sighup
- Measured default
- Empty string
- Unit
- —
- Metadata snapshot
- 18
Definition PG 18 manual
Specifies the name of the file containing the SSL client certificate revocation list (CRL). Relative paths are relative to the data directory. This parameter can only be set in the postgresql.conf file or on the server command line. The default is empty, meaning no CRL file is loaded (unless ssl_crl_dir is set).
Measured default history
| Version interval | Default |
|---|---|
| 9.2 – 19 | Empty string |
Authored guidance from the GUC source snapshot; the version-specific manual above is the definition reference. View source ↗
How it works
ssl_crl_file identifies the location of the SSL certificate revocation list file. The PEM revocation list is consulted when validating client certificates and must be refreshed as issuers publish new revocation state.
ssl_crl_file 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_crl_file 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_crl_file globally without a rollback plan and a client or operational compatibility test.
Workload guidance
OLAP: Analytical clients follow the same revocation policy; do not defer CRL refresh because their sessions are longer or less frequent.
OLTP: Refresh ssl_crl_file from the issuing CA before its next-update deadline, validate its signature and issuer coverage, reload PostgreSQL, and prove that a newly revoked client certificate is rejected.
SMALL: If a managed CRL feed is unavailable, document that client-certificate revocation is not current rather than relying on a stale file. Keep the file and reload process monitored on every failover node.
Version history 4
- PG 13 → 14changed
- PG 10 → 11changed
- PG 9.6 → 10changed
- PG 9.1 → 9.2added
Related entries
Further reading
Definition snapshot: english-manuals:adf50ce4fab892927b872b686ec… · English manual source