Re: pgsql: pg_rewind: Fix determining TLI when server was just promoted.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: pg_rewind: Fix determining TLI when server was just promoted.
Date: 2023-02-27 16:57:04
Message-ID: CA+Tgmob5CP05opFrbXEety8d=ZAsmHtQ8X4Y6BLQA3yiG7U+tg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Thu, Feb 23, 2023 at 8:40 AM Heikki Linnakangas
<heikki(dot)linnakangas(at)iki(dot)fi> wrote:
> This is arguably a bug fix, but don't backpatch because we haven't
> really treated it as a bug so far.

I guess I'm having trouble understanding why this is only arguably a
bug fix. Seems like flat-out wrong behavior.

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2023-02-27 21:30:04 pgsql: Harden postgres_fdw tests against unexpected cache flushes.
Previous Message Heikki Linnakangas 2023-02-27 08:02:24 pgsql: Replace single-quotes with double-quotes in a few SGML attribute

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-02-27 16:59:20 Re: Stale references to guc.c in comments/tests
Previous Message Tom Lane 2023-02-27 16:20:34 Re: pg_dump versus hash partitioning