From: | "Medi Montaseri" <montaseri(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | PG engine takeover or switch over |
Date: | 2007-08-15 19:30:15 |
Message-ID: | 8078a1730708151230t2b9542aaxe6703bb2c61b778f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Hilton Perantunes | 2007-08-15 20:13:41 | Yet Another Socket .s.PGSQL.5432 Problem |
Previous Message | Peter Koczan | 2007-08-15 18:39:30 | Re: Configure pg_hba.conf |