Re: [GENERAL] Failover architecture

2011-08-18 Thread Reuven M. Lerner
Thanks, Tatsuo, and others who commented so helpfully.  It's the best of all worlds when I get confirmation that my feelings were right, *and* I learn a lot of new things that I had never considered, thanks to the generosity of this great community. Reuven

Re: [GENERAL] Failover architecture

2011-08-17 Thread Tatsuo Ishii
> Of course, Is there any easy way to do that?  If so, then what > happens when pgpool tries forward an INSERT to the master while > it's in read-only mode? Assuming "read-only mode" is a database running in read-only transaction mode(like standby), you will get errors someth

Re: [GENERAL] Failover architecture

2011-08-17 Thread Craig Ringer
I can't help so much with the Pg replication specific parts, but this I can answer: On 17/08/2011 9:25 PM, Reuven M. Lerner wrote: restart streaming, it goes back into read-write mode. Is there a way (other than Bucardo, which doesn't seem to fit the bill for this project), is ther

Re: [GENERAL] Failover architecture

2011-08-17 Thread John R Pierce
On 08/17/11 6:25 AM, Reuven M. Lerner wrote: * Once the slave has been promoted to master, we have a single server, and a single point of failure. Is there any simple way to get the former master to become a slave? I assume that it would need to start the whole becoming-a-slave p

[GENERAL] Failover architecture

2011-08-17 Thread Reuven M. Lerner
Hi, everyone.  I'm working on a project that is already using PostgreSQL 9.0, including streaming replication.  I'm trying to help them figure out a good architecture for ensuring stability and failover under a variety of conditions, and wanted to ask the community for su