| From: | Daniel Gustafsson <dgustafsson(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Extend the private key stat checking error handling |
| Date: | 2021-11-30 22:31:00 |
| Message-ID: | E1msBeO-0000eW-Qi@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Extend the private key stat checking error handling
If the stat operation on the private key failed, the code assumed it
was due to an ENOENT, which may or may not be true. Extend the check
by printing a different error message on non-ENOENT errors for easier
debugging.
Per suggestion by Tom Lane due to an issue with the fairywren animal
in the buildfarm.
Discussion: https://postgr.es/m/1632478.1638305700@sss.pgh.pa.us
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/538724fc36e05339ea3734f1b886a67398fce71a
Modified Files
--------------
src/interfaces/libpq/fe-secure-openssl.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-12-01 02:05:00 | pgsql: Improve psql tab completion for various DROP commands |
| Previous Message | Tom Lane | 2021-11-30 22:18:17 | pgsql: Cope with cross-compiling when checking for a random-number sour |