Re: Question about StartLogicalReplication() error path - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Question about StartLogicalReplication() error path
Date
Msg-id CA+TgmoaB7JD30=SGE+8odTEjxAPaPEn=B2oE7k=QA9AYviKRbg@mail.gmail.com
Whole thread Raw
In response to Re: Question about StartLogicalReplication() error path  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Question about StartLogicalReplication() error path  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Mon, Jun 14, 2021 at 12:50 PM Jeff Davis <pgsql@j-davis.com> wrote:
> It seems that there's not much agreement in a behavior change here. I
> suggest one or more of the following:
>
>  1. change the logical rep protocol docs to match the current behavior
>     a. also briefly explain in the docs why it's different from
> physical replication (which does always start at the provided LSN as
> far as I can tell)
>
>  2. Change the comment to add something like "Starting at a different
> LSN than requested might not catch certain kinds of client errors.
> Clients should be careful to check confirmed_flush_lsn if starting at
> the requested LSN is required."
>
>  3. upgrade DEBUG1 message to a WARNING
>
> Can I get agreement on any of the above suggestions?

I'm happy to hear other opinions, but I think I would be inclined to
vote in favor of #1 and/or #2 but against #3.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Race condition in recovery?
Next
From: Tom Lane
Date:
Subject: Re: recent failures on lorikeet