Re: Non-null values of recovery functions after promote or crash of primary

From: Martín Marqués <martin(at)2ndquadrant(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Non-null values of recovery functions after promote or crash of primary
Date: 2019-10-08 19:56:38
Message-ID: CAPdiE1xtC7y1y7tawhu4NzVysfGGdwYq-FswjXQXvS9RMd4-1A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Hi,

> IMV, and not unlike other similar cases I've talked about on another
> thread, these should be cleared when the system is promoted as they're
> otherwise confusing and nonsensical.

Keep in mind that this also happens when the server crashes and has to
perform crash recovery. In that case the server was always a primary.

--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2019-10-09 01:49:55 Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
Previous Message Stephen Frost 2019-10-08 18:03:02 Re: Non-null values of recovery functions after promote or crash of primary

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-10-08 20:25:05 Re: pgsql: Remove pqsignal() from libpq's official exports list.
Previous Message Robert Haas 2019-10-08 18:45:41 Re: Transparent Data Encryption (TDE) and encrypted files