Re: pg_recvlogical prints bogus error when interrupted - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_recvlogical prints bogus error when interrupted
Date
Msg-id ZLiBEm3IQDERNx70@paquier.xyz
Whole thread Raw
In response to Re: pg_recvlogical prints bogus error when interrupted  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
On Wed, Jul 19, 2023 at 01:33:15PM +0530, Bharath Rupireddy wrote:
> I think the delay is expected for the reason specified below and is
> not because of any of the changes in v5. As far as CTRL+C is
> concerned, it is a clean exit and hence we can't escape the while(1)
> loop.

Yes, that's also what I am expecting.  That's costly when replaying a
large change chunk, but we also want a clean exit on a signal as the
code comments document, so..
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Performance degradation on concurrent COPY into a single relation in PG16.
Next
From: Michael Paquier
Date:
Subject: Re: pg_recvlogical prints bogus error when interrupted