Re: is sync rep stalled?

From: Aidan Van Dyk <aidan(at)highrise(dot)ca>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: David Fetter <david(at)fetter(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: is sync rep stalled?
Date: 2010-10-05 13:33:57
Message-ID: AANLkTikH-K1q+4f5ypQ+e=zXnf2F4B7xqisHB4TxAmrH@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 4, 2010 at 11:48 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:

> How can we take a base backup for that synchronous standby? You mean
> that we should disable the wait-forever option, start the master, take
> a base backup, shut down the master, enable the wait-forever option,
> start the master, and start the standby from that base backup?

All I'm saying is that *after* you've configured that everything must
be synchronous is *not* the time to start trying to figure out if your
PITR backups/archive are working, and starting to try and get a slave
replicating synchronously.

Yes, High-Durability sync rep has caveats. One of them is that you
must have a working synchronous slave before you can enforce
synchronousity.

a.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2010-10-05 13:39:38 Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)
Previous Message Robert Haas 2010-10-05 13:12:05 Re: Insertion of geometric type column with column[0], column[1] and etc.