From: KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>
To: fabriziomello@gmail.com
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Time-Delayed Standbys
Date: Mon, 09 Dec 2013 19:51:01 +0900
Message-ID: <52A5A095.5020002@lab.ntt.co.jp> (raw)
In-Reply-To: <52A59D10.7020209@lab.ntt.co.jp>
References: <CAFcNs+oXq5ZPaKARRn3VZGzX+AnTZCaEjR6VmQT_tvoFiqgaSg@mail.gmail.com>
<CA+U5nML64Y7Nf0mpQirk-tOWrV+ZQ3y8DdRgk2mP+e3kGT16Mw@mail.gmail.com>
<CAFcNs+rAJO6wvzN8zQCTUpii0mC9Ax51JxVhWTsos7xsFdwXjw@mail.gmail.com>
<CA+TgmoaCL4G+YotjjjFM+J_h0nSkp4gXiiBPDQGHxTcc_T0w-w@mail.gmail.com>
<CAFcNs+r-GyizHAPDvRz=3XR3BYLUqxpqxrvJq8spk4PJe5hxAA@mail.gmail.com>
<52A59D10.7020209@lab.ntt.co.jp>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
(2013/12/09 19:36), KONDO Mitsumasa wrote:
> * Problem 1
> I read your wittened document. There is "PITR has not affected".
> However, when I run PITR with min_standby_apply_delay=3000000, it cannot start
> server. The log is under following.
>> [mitsu-ko@localhost postgresql]$ bin/pg_ctl -D data2 start
>> server starting
>> [mitsu-ko@localhost postgresql]$ LOG: database system was interrupted; last
>> known up at 2013-12-08 18:57:00 JST
>> LOG: creating missing WAL directory "pg_xlog/archive_status"
>> cp: cannot stat `../arc/00000002.history':
>> LOG: starting archive recovery
>> LOG: restored log file "000000010000000000000041" from archive
>> LOG: redo starts at 0/41000028
>> LOG: consistent recovery state reached at 0/410000F0
>> LOG: database system is ready to accept read only connections
>> LOG: restored log file "000000010000000000000042" from archive
>> FATAL: cannot wait on a latch owned by another process
>> LOG: startup process (PID 30501) exited with exit code 1
>> LOG: terminating any other active server processes
> We need recovery flag for controling PITR situation.
Add my comment. We have to consider three situations.
1. PITR
2. replication standby
3. replication standby with restore_command
I think this patch cannot delay in 1 situation. So I think you should add only
StandbyModeRequested flag in conditional branch.
Regards,
--
Mitsumasa KONDO
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: kondo.mitsumasa@lab.ntt.co.jp, fabriziomello@gmail.com, robertmhaas@gmail.com, simon@2ndquadrant.com
Subject: Re: Time-Delayed Standbys
In-Reply-To: <52A5A095.5020002@lab.ntt.co.jp>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox