[pgpool-hackers: 16] Re: [Pgpool-hackers] proposal for new feature
Tatsuo Ishii
ishii at postgresql.org
Thu Dec 29 09:24:22 JST 2011
Hi Mitani-san,
Any progress on this?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
> Yes, basically, (1) and (2) should be in configuration file.
> However, if pgpool required dynamically adding to system,
> these basic informations might be in a shared repository.
>
> Regards,
> --
> At.Mitani
>
> On Mon, 21 Nov 2011 21:46:15 +0100
> Guillaume Lelarge <guillaume at lelarge.info> wrote:
>
>> On Mon, 2011-11-21 at 10:48 +0900, mitani at sraw.co.jp wrote:
>> > Hi Guillaume,
>> > Thank you for quick comments.
>> >
>> > I think some informations are required for redundancy as follows,
>> > (1) the basic information of each pgpool like a port and IP address etc.
>> > (2) the basic information of DB servers like a port, IP address etc.
>> > (3) the status of each pgpool like a master/slave and running/standby/stop etc.
>> > (4) the status of DB servers like a master/slave and running/standby/stop etc.
>> >
>> > I think that the redundant process might be work based on these informations.
>> >
>>
>> Well, 1, and 2 should be in configuration files. 3, and 4 seem more
>> likely to be required in a shared pool of informations.
>>
>>
>> --
>> Guillaume
>> http://blog.guillaume.lelarge.info
>> http://www.dalibo.com
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus signature database 6649 (20111121) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>
>
> --
> mitani <mitani at sraw.co.jp>
More information about the pgpool-hackers
mailing list