[pgpool-general: 2509] Re: Common practices for pgpool availability and data replication

[Lazaro Ruben Garcia Martinez]

For number one you should use watchdog functionality.

Regards.
________________________________________
De: pgpool-general-bounces at pgpool.net [pgpool-general-bounces at pgpool.net] En nombre de Athanasios | ZenGuard [athanasios at zenguard.org]
Enviado el: jueves, 30 de enero de 2014 6:48
Para: Gintautas Sulskus
CC: pgpool-general at pgpool.net
Asunto: [pgpool-general: 2505] Re: Common practices for pgpool availability and data replication

Hi,
for point 1) you can use keepalived and two pgpool machines


On Thu, Jan 30, 2014 at 12:00 PM, Gintautas Sulskus <gingaz at gmail.com<mailto:gingaz at gmail.com>> wrote:
Dear All,

I have a few questions regarding practices with pgpool:
1. Typically pgpool is a single point of failure. What is the common practice to solve this?
2. Some of our data (e.g. 10% tables) must be consistent across the cluster for every transaction. The rest may differ. Is it possible to have a fine-grained replication, where some DMLs would be replicated synchronously and the rest would use asynchronous replication?

Thanks!

Best Regards,
Gintautas

_______________________________________________
pgpool-general mailing list
pgpool-general at pgpool.net<mailto:pgpool-general at pgpool.net>
http://www.pgpool.net/mailman/listinfo/pgpool-general



________________________________
Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU!
http://www.antiterroristas.cu
http://justiciaparaloscinco.wordpress.com

Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU!
http://www.antiterroristas.cu
http://justiciaparaloscinco.wordpress.com