Re: Reading timeline from pg_control on replication slave

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reading timeline from pg_control on replication slave
Date: 2017-10-30 06:29:00
Message-ID: CAB7nPqQ8HffwDQwwg5_Z_NsFqk8VnyioyXydNPivHU8F-WWvEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 30, 2017 at 2:48 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> (I'd quite like ThisTimeLineID to go away as a global. It's messy and
> confusing, and I'd much rather it be fetched when needed).

Yeah, I agree. My take on the matter is that we could just use the
status data of the control file which is in shared memory as the only
writers to it are the checkpointer and the startup processes.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-10-30 06:50:25 Re: path toward faster partition pruning
Previous Message Masahiko Sawada 2017-10-30 06:17:59 Re: Moving relation extension locks out of heavyweight lock manager