From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BF animal malleefowl reported an failure in 001_password.pl |
Date: | 2023-01-25 02:09:39 |
Message-ID: | CA+hUKGLW0dx7OBctU-oKk6r0-WHWEV9Z1GJ8V=Z5sCc3x3p1HA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jan 20, 2023 at 9:16 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> > So I think we probably need something like the attached, which I was
> > originally trying to avoid.
>
> Yeah, something like that. I also wonder if you don't need to think
> a bit harder about the ordering of the flag checks, in particular
> it seems like servicing reload_request before child_exit might be
> a good idea (remembering that child_exit might cause launching of
> new children, so we want to be up to speed on relevant settings).
Agreed, and done.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2023-01-25 02:32:46 | Re: plpython vs _POSIX_C_SOURCE |
Previous Message | Andres Freund | 2023-01-25 01:48:56 | Re: plpython vs _POSIX_C_SOURCE |