Message-ID: <4F68E989.7080101@d2.com>
Date: Tue, 20 Mar 2012 13:33:13 -0700
From: amador alvarez <aalvarez@d2.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US;
	rv:1.9.2.27) Gecko/20120216 Lightning/1.0b2 Thunderbird/3.1.19
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Re: clustering with shared storage
References: 
 <CAEHjwJ7qWN05=cte4nLGV+XKKQragFjJaZiMEC-x0BtEJBN5Wg@mail.gmail.com>
	<1332273497.2427.17.camel@lenovo01-laptop03.gunduz.org>
In-Reply-To: <1332273497.2427.17.camel@lenovo01-laptop03.gunduz.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi there,
I wonder why are you considering this solution, as if something wrong=20
comes within the data (logical corruption, user error) it will be spread=20
on both locations, Would not be better a delayed standby database.

I am curious because I am setting this up right now and do not get all=20
the advantages of the shared disk solution,

Thanks in advance,
AA

On 03/20/2012 12:58 PM, Devrim G=C3=9CND=C3=9CZ wrote:
> Hi,
>
> On Tue, 2012-03-20 at 15:26 -0400, Gary Webster wrote:
>
>> The best I've found is here:
>> http://wiki.postgresql.org/images/5/58/06.5_-_Devrim_Gunduz_-_PostgreS=
QLClusteringWithRedHatClusterSuite--LT.pdf
>> but, it doesn't go into setup details.
> http://www.gunduz.org/download.php?dlid=3D190
>
> has a newer version (still not that detailed, but much better)
>
>> I have a few questions/issues, but figure I will attack it piecemeal, =
in
>> chronological order.
>>
>> RHCS is handling the fencing.
>> I have installed postgres on the local drive of the primary, with pgda=
ta on
>> the shared drive.
>> I am generally using the EnterpriseDB install package for v9.1.3 .
>>
>> So, first, just how to install postgres on the secondary?
> Just install the binaries -- don't initdb, and then use the shared disk
> as the $PGDATA. RHCS will mount the shared filesystem to only one
> server, and that one will use the $PGDATa.
>
>> 1)  If I leave it as secondary (non-active), it can't see the shared d=
rive.
>>   Is this correct/OK ?
> It *can* see, but it does not see (or it should not see) and it *cannot=
*
> use.
>
>> If so, it will create its own pgdata locally, which is later ignored?
>>
>> or
>>
>> 2)  Do I make it primary, then point its pgdata to the already existin=
g
>> data during install ?!?
> See above.
>
> Regards,