Re: Is RecoveryConflictInterrupt() entirely safe in a signal handler?

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, Noah Misch <noah(at)leadboat(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Is RecoveryConflictInterrupt() entirely safe in a signal handler?
Date: 2023-08-05 02:53:09
Message-ID: CA+hUKGKEtbF1t9N_e_K2UiY+HGjGtKausm44oajinJHoMcfjYA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Aug 5, 2023 at 1:39 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Here is a rebase over 26669757, which introduced
> PROCSIG_RECOVERY_CONFLICT_LOGICALSLOT.

Oops, please disregard v7 (somehow lost a precious line of code). V8 is better.

Attachment Content-Type Size
v8-0001-Fix-recovery-conflict-SIGUSR1-handling.patch text/x-patch 20.0 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2023-08-05 03:16:11 Re: pgbench: allow to exit immediately when any client is aborted
Previous Message Thomas Munro 2023-08-05 01:42:33 Re: A failure in 031_recovery_conflict.pl on Debian/s390x