pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hannes Dorbath <light@theendofthetunnel.de>
To: Medi Montaseri <montaseri@gmail.com>
Subject: Re: PG engine takeover or switch over
Date: Thu, 16 Aug 2007 09:13:53 +0200
Message-ID: <46C3F931.2040502@theendofthetunnel.de> (raw)
In-Reply-To: <8078a1730708151230t2b9542aaxe6703bb2c61b778f@mail.gmail.com>
References: <8078a1730708151230t2b9542aaxe6703bb2c61b778f@mail.gmail.com>

On 15.08.2007 21:30, Medi Montaseri wrote:
> I am looking for some suggestions to optimize the following
> problem/solution.
> 
> Given two nodes A and B (two computers) in a active-passive mode where A is
> running PG engine,  and B is simply standing by,  and  a common storage
> (twin tailed) ( or from pg_ctl point of view -D /common/data ), I am looking
> for a faster solution during the takeover where A has crashed and B is to
> start PG engine and run with it.
> 
> My current solution is to start PG engine which should take little time to
> study the configuration files and /common/data and fork a few childrens. But
> I am still interested in optimizing this start-up cost.
> 
> For example, would I gain anything by starting PG engine on both A and B,
> but on B I point it to /common/dummy and during the takeover, I somehow tell
> it to now read from /common/data, for example have two postmaster.conf or
> PGDATA and then use  pg_ctl reload.

Starting up PostgreSQL should be very fast, given no recovery to be done 
and decent hardware.

PostgreSQL does not fork a lot unless it is accepting new connections 
and if reading a config file is slow on your system, something else is 
broken.

In a active/passive setup your should be able to switch over in under 3 
seconds. If there was a lot of load on the failed node the recovery 
times on the new active node increase. The only thing you can do about 
that is getting faster disks..


-- 
Regards,
Hannes Dorbath



view thread (4+ messages)  latest in thread

Message-ID: <46C3F931.2040502@theendofthetunnel.de>
Permalink:  ../46C3F931.2040502@theendofthetunnel.de/
Also on:    postgresql.org/message-id/46C3F931.2040502@theendofthetunnel.de

 · 

reply

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-admin@postgresql.org
  Cc: light@theendofthetunnel.de, montaseri@gmail.com
  Subject: Re: PG engine takeover or switch over
  In-Reply-To: <46C3F931.2040502@theendofthetunnel.de>

* 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