Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 69CAD9FB534 for ; Wed, 15 Aug 2007 16:30:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 07246-02 for ; Wed, 15 Aug 2007 16:30:18 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by postgresql.org (Postfix) with ESMTP id C485D9FB4FB for ; Wed, 15 Aug 2007 16:30:18 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id u77so46073pyb for ; Wed, 15 Aug 2007 12:30:16 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=TUC8S4nMvwHprMFr9yMh64Ex3Lg0ndZ/An5abGk2YnbJGYedp1A/UKA0yx6yGXVB+F8ywJKZiLXRYpfRkOmAePcybRbQX5wjBRf91DhnlJnkL2xl4BQNDgGE+W6PPOczFaY+AbPY3g+rpTOsV28sBTSj2kmRIcJv/eXsgLvao4c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=RiQ5VcSXDP1X13+Z/jNEZqmJ++1YkKDpme4vFKMo8oRZeYN2Z+vLiblLBb97TLZhRfT4U1Is7IXc9kdjvvc3r0q7cvV/3JFGxCWw1raeWUbfQ6Igf7pCOrrlBA8uLMww7uhBo+Yt+DH8mFVHthB2miA/G5Ta/D+AuhNYqM3zSBc= Received: by 10.64.91.15 with SMTP id o15mr1610753qbb.1187206216043; Wed, 15 Aug 2007 12:30:16 -0700 (PDT) Received: by 10.65.110.15 with HTTP; Wed, 15 Aug 2007 12:30:15 -0700 (PDT) Message-ID: <8078a1730708151230t2b9542aaxe6703bb2c61b778f@mail.gmail.com> Date: Wed, 15 Aug 2007 12:30:15 -0700 From: "Medi Montaseri" To: pgsql-admin@postgresql.org Subject: PG engine takeover or switch over MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_73409_15887312.1187206215580" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/186 X-Sequence-Number: 26517 ------=_Part_73409_15887312.1187206215580 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 ------=_Part_73409_15887312.1187206215580 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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
------=_Part_73409_15887312.1187206215580--