| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <fujii(at)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Weird failure with latches in curculio on v15 |
| Date: | 2023-02-03 09:24:18 |
| Message-ID: | 0CA603B0-0B95-4FB7-B3A5-84BB60F3C2C4@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On February 3, 2023 9:19:23 AM GMT+01:00, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
>On Fri, Feb 3, 2023 at 9:09 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
>> Thinking about popen() suggests that we have a similar problem with COPY
>> FROM PROGRAM as we have in pgarch (i.e. not as bad as the startup
>> process issue, but still not great, due to
>> procsignal_sigusr1_handler()).
>
>A small mercy: while we promote some kinds of fatal-ish signals to
>group level with kill(-PID, ...), we don't do that for SIGUSR1 for
>latches or procsignals.
Not as bad, but we still do SetLatch() from a bunch of places that would be reached...
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | wangw.fnst@fujitsu.com | 2023-02-03 09:42:34 | RE: Time delayed LR (WAS Re: logical replication restrictions) |
| Previous Message | jacktby@gmail.com | 2023-02-03 09:18:50 | Where is the logig to create a table file? |