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@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
