Re: "Hot standby"?

From: Gianni Ciolli <gianni(dot)ciolli(at)2ndquadrant(dot)it>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: "Hot standby"?
Date: 2009-08-11 22:54:49
Message-ID: 20090811225449.GA23151@eee.gi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 12, 2009 at 12:11:28AM +0300, Peter Eisentraut wrote:
> On Tuesday 11 August 2009 18:16:04 Gianni Ciolli wrote:
> > As for "warm/hot", it depends on what you exactly mean with "get
> > ready":
> >
> > (A) If you mean "it is possible to connect to the second node", then
> > Simon's patch is "hot".
>
> Yeah, but by that definiton doing a pg_dump/pg_restore every hour is also
> "hot". ;-)

OK, but only if (a) the data is so small that the restore takes less
than one hour, and if (b) the workload is far from 100% ;-)

Since there seem to be multiple views about terminology, it may be
useful to recall the proposed wording from
http://wiki.postgresql.org/wiki/Hot_Standby :

* the first node is called either "Primary" or "Master"

* the second node is called "Standby"

* the Standby is referred to as a "Clone" instead of a "Slave", to
mean that it is an exact copy, which, instead of being built by
repeating the actions of the master, is constructed just by
implementing their effects.

Best regards,
Dr. Gianni Ciolli - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gianni(dot)ciolli(at)2ndquadrant(dot)it | www.2ndquadrant.it

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul Matthews 2009-08-11 22:58:19 Re: Quick pointer required re indexing geometry
Previous Message David Fetter 2009-08-11 22:31:34 Collation