From: Medi Montaseri <montaseri@gmail.com>
To: pgsql-admin@postgresql.org
Subject: PG engine takeover or switch over
Date: Wed, 15 Aug 2007 12:30:15 -0700
Message-ID: <8078a1730708151230t2b9542aaxe6703bb2c61b778f@mail.gmail.com> (raw)
Hi,
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.
Thanks
Medi
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: montaseri@gmail.com
Subject: Re: PG engine takeover or switch over
In-Reply-To: <8078a1730708151230t2b9542aaxe6703bb2c61b778f@mail.gmail.com>
* 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