On Tue, 2013-01-15 at 11:28 +0900, yusuke iida wrote:
> Hi, Jiaju
>
> 2013/1/11 Jiaju Zhang :
> > Hi Yusuke,
> >
> > Sorry for the late reply;)
> >
> > On Mon, 2013-01-07 at 13:50 +0900, yusuke iida wrote:
> >> Hi, Jiaju
> >>
> >> When the proposal was conflict, I want to keep on the site of the
>
Hi Jiaju,
2013/1/14 Jiaju Zhang :
> Hi Yuichi,
>
> Thanks for the patch!
>
> However, I need to say some coding style problem first;) I didn't say
> this before, so it seems a little bit messy and will confuse a lot of
> contributors and users, sorry for the inconvenience;)
>
> Now I'd like to say
Thank you Takatoshi,
I appreciate your help on this. I just got pulled onto another project, but
will be coming back to this in a few days. I thought I had tried this, but had
issues consistently getting test-db1 to come up initially. I need to debug that
further. I had the configuration the
Hi, Jiaju
2013/1/11 Jiaju Zhang :
> Hi Yusuke,
>
> Sorry for the late reply;)
>
> On Mon, 2013-01-07 at 13:50 +0900, yusuke iida wrote:
>> Hi, Jiaju
>>
>> When the proposal was conflict, I want to keep on the site of the
>> original lease.
>> I do not want to generate a revoke when maintained.
>>
Hi Keith
> When I set the master_ip as the Cluster IP, Postgres does not come up because
> it is looking for the virtual IP that is dependant of Postgres master. Kind
> of a catch 22?
Slave's PostgreSQL ?
Slave connects to Virtual IP which is started on Master,
so it's normal.
Please check pg_h
