| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Gurjeet Singh <gurjeet(at)singh(dot)im>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_reload_conf() synchronously |
| Date: | 2022-11-05 03:35:21 |
| Message-ID: | 2527794.1667619321@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> Worth noting that this doesn't necessarily suffice to avoid race conditions in
> tests, if the test depends on *other* backends having seen the configuration
> changes.
True, but do we have any such cases?
> It might be worth to use the global barrier mechanism to count which backends
> have reloaded configuration and to provide a function / option to pg_sleep
> that waits for that.
That ... seems like a lot of mechanism. And it could easily result
in undetected deadlocks, if any other session is blocked on you.
I seriously doubt that we should go there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-11-05 04:51:08 | Re: pg_reload_conf() synchronously |
| Previous Message | Michael Paquier | 2022-11-05 03:34:02 | Re: Incorrect include file order in guc-file.l |