Re: "Hot standby"?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Greg Stark" <gsstark(at)mit(dot)edu>
Cc: "Josh Berkus" <josh(at)agliodbs(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Mark Mielke" <mark(at)mark(dot)mielke(dot)cc>, "Bruce Momjian" <bruce(at)momjian(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "Hot standby"?
Date: 2009-08-12 15:12:28
Message-ID: 4A82958C0200002500029944@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Stark <gsstark(at)mit(dot)edu> wrote:

> I'm not actually certain we can handle streaming synchronous mode to
> a standby slave. Does the slave need to have connections enabled to
> handle feeding wal sync status to the master?

I thought there were major concerns about the interaction of those
read-only queries with the replicated database transactions in
synchronous mode, too. Following threads on the topic has left me a
little dubious that it can be truly synchronous, in the sense that it
must commit to the clone before the master returns an indication of
success to the client. Are we still shooting for that or has
"synchronous" become shorthand for "we'll try really hard to keep the
lag minimal when we can"?

> I don't see any particular reason to come up with names for each of
> these combination of modes. I'm pretty happy just saying there are
> three different configuration options and certain options depend on
> other options so only certain combinations are legal.

Sounds reasonable to me.

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-08-12 15:14:32 Re: machine-readable explain output v4
Previous Message Andrew Dunstan 2009-08-12 15:11:36 Re: machine-readable explain output v4