From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Gurjeet Singh <gurjeet(at)singh(dot)im>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Patch: Don't set LoadedSSL unless secure_initialize succeeds |
Date: | 2022-05-24 03:51:25 |
Message-ID: | 1413636.1653364285@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> On 22 May 2022, at 08:41, Gurjeet Singh <gurjeet(at)singh(dot)im> wrote:
>> The initialization in PostmasterMain() blindly turns on LoadedSSL,
>> irrespective of the outcome of secure_initialize().
> This call is invoked with isServerStart set to true so any error in
> secure_initialize should error out with ereport FATAL (in be_tls_init()). That
> could be explained in a comment though, which is currently isn't.
The comments for secure_initialize() and be_tls_init() both explain
this already.
It's not great that be_tls_init() implements two different error
handling behaviors, perhaps. One could imagine separating those.
But we've pretty much bought into such messes with the very fact
that elog/ereport sometimes return and sometimes not.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2022-05-24 03:58:12 | Re: partition wise aggregate wrong rows cost |
Previous Message | bucoo | 2022-05-24 03:38:14 | partition wise aggregate wrong rows cost |