| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Redesigning postmaster death handling |
| Date: | 2025-08-21 05:45:41 |
| Message-ID: | 1377623.1755755141@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Following that line of thinking, we might as well just ask the kernel
> to hit our existing SIGQUIT handler at parent exit, on Linux/FreeBSD.
> Job done.
One other thought here: do we *really* want such a critical-and-hard-
to-test aspect of our behavior to be handled completely differently
on different platforms? I'd lean to ignoring the Linux/FreeBSD
facilities, because otherwise we're basically doubling our testing
problems in exchange for not much.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2025-08-21 06:01:15 | Re: Conflict detection for update_deleted in logical replication |
| Previous Message | Hayato Kuroda (Fujitsu) | 2025-08-21 05:41:09 | RE: memory leak in logical WAL sender with pgoutput's cachectx |