| From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgpool question |
| Date: | 2005-03-10 04:43:18 |
| Message-ID: | Pine.GSO.4.62.0503100742180.26616@ra.sai.msu.su |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 10 Mar 2005, Tatsuo Ishii wrote:
>>>
>>> However it would be easy to modify pgpool to allow automatic switch
>>> back (with a risk of unwanted repeating switching, of course). Is
>>> this what you want?
>>
>> No, your arguments are important. I don't want too much intelligence, but
>> when I restart primary backend by hand I don't see any problem to
>> switch pgpool back using -s m switch (also by hand). For brave, probably,
>> something like --auto would fine.
>
> Problem is, the communication infrastructure between pgpool master
> process and another pgpool process which you started by hand to switch
> is very poor. Currently signal is used to tell the pgpool master
> process to switch/fail over. Apparently we need more info (for example
> the signal is sent by DBA, not because of a failure detected by a
> pgpool child process).
>
> To fix the problem we need shared memory, pipe, socket or whatever
> to pass info and it will not be a trivial fix so will take some
> time...
may be telnet interface ?
> --
> Tatsuo Ishii
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-10 04:44:55 | Re: We are not following the spec for HAVING without GROUP |
| Previous Message | Tatsuo Ishii | 2005-03-10 04:35:59 | Re: pgpool question |