Prashanth Ranjalkar <prashant.ranjalkar@xxxxxxxxx> wrote: >> Hello, Could explain somebody what will happen, if the slave > It depends on the type of replication is used. > > If it's a slony replication then master continues to work and > will catch up when slave is available. > > However if the Streaming replication is used, [...] once it fills > all the space, master may go down. That strikes me a false distinction -- Slony also stores data to be replicated until the slave becomes available. Either way you can control where that is stored, and you need to watch out for space problems on an extended outage of a replica. An issue I don't think I've seen mentioned is that if you use synchronous replication you are telling PostgreSQL not to return an indication of success for a data-modifying transaction until the work of that transaction has been persisted on at least one replica. To avoid stalls on the master, you may want to define multiple synchronous replicas, so that when one goes down you keep running without DBA intervention. -- Kevin Grittner EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
