Re: Hot Standby on git

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hot Standby on git
Date: 2009-10-02 07:04:47
Message-ID: 4AC5A60F.5050503@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
> @@ -7061,6 +7061,15 @@ ShutdownXLOG(int code, Datum arg)
> else
> {
> /*
> + * Take a snapshot of running transactions and write this to WAL.
> + * This allows us to reconstruct the state of running transactions
> + * during archive recovery, if required. We do this even if we are
> + * not archiving, to allow a cold physical backup of the server to
> + * be useful as a read only standby.
> + */
> + GetRunningTransactionData();
> +
> + /*
> * If archiving is enabled, rotate the last XLOG file so that all the
> * remaining records are archived (postmaster wakes up the archiver
> * process one more time at the end of shutdown). The checkpoint
>

I don't think this will do any good where it's placed. The checkpoint
that follows will have its redo-pointer beyond the running-xacts record,
so WAL replay will never see it.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2009-10-02 07:32:10 Re: Hot Standby on git
Previous Message Simon Riggs 2009-10-02 06:53:51 Re: FSM search modes