| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Can a child process detect postmaster death when in pg_usleep? |
| Date: | 2021-07-02 01:27:21 |
| Message-ID: | YN5reTSMBP0Vg10k@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 28, 2021 at 11:01:57AM -0400, Tom Lane wrote:
> Dunno ... I cannot recall ever having had that as a debugging requirement
> in a couple of decades worth of PG bug-chasing. If the postmaster is
> dying, you generally want to deal with that before bothering with child
> processes. Moreover, child processes that don't go awy when the
> postmaster does are a very nasty problem, because they could screw up
> subsequent debugging work.
At the same time, nobody has really complained about this being an
issue for developer options. I would tend to wait for more opinions
before doing anything with the auth_delay GUCs.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2021-07-02 01:29:01 | Re: Commit fest manager |
| Previous Message | Jeremy Schneider | 2021-07-02 01:25:58 | relation OID in ReorderBufferToastReplace error message |