From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Keiko Oda <keiko713(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Trigger file behavior with the standby |
Date: | 2018-03-20 04:28:18 |
Message-ID: | 20180320042818.GA13368@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Mar 19, 2018 at 01:27:21PM -0700, Keiko Oda wrote:
> I'm seeing the following behavior with a trigger file which is very
> confusing to me, I'd like to get some advice of what is the expected
> behavior of the trigger file with the standby.
This portion from the docs includes your answer:
https://www.postgresql.org/docs/devel/static/warm-standby.html#STANDBY-SERVER-OPERATION
"Standby mode is exited and the server switches to normal operation when
pg_ctl promote is run or a trigger file is found (trigger_file). Before
failover, any WAL immediately available in the archive or in pg_wal will
be restored, but no attempt is made to connect to the master.
So when creating a trigger file or signaling for promotion, any WAL
files available are first fetched, and then promotion happens. In your
case all the WAL segments from the archives are retrieved first.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2018-03-20 04:30:26 | Re: ON CONFLICT DO UPDATE for partitioned tables |
Previous Message | Tom Lane | 2018-03-20 04:01:02 | Re: IndexJoin memory problem using spgist and boxes |