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, Matser continues to work if slave is unavailable till it finds space for WAL archiving on master, depends on the archieving strategy that implemented while configuring replication. WAL's keep accumulating on the master server till it applies to Slave server after it is available. As long as it find space on master, there is no impact but once it fills all the space, master may go down. ** *Thanks & Regards,* *** * *Prashanth Ranjalkar* *Database Consultant & Architect* *www.postgresdba.net* On Wed, Feb 20, 2013 at 9:34 PM, Viktor <vik...@okservers.eu> wrote: > Ook, thanks =) > > > On 2/20/2013 5:56 PM, Gilberto Castillo wrote: > > Hello, > > Could explain somebody what will happen, if the slave server fails ? > Will it affect the master functionality/availability ? > > nothing!!! the Master continuo work. ;-))) > > > I'm using simple master-slave replication with 2 servers. > > > -- > Best regards > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your > subscription:http://www.postgresql.org/mailpref/pgsql-admin--- > This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE > running at host imx2.etecsa.cu > Visit our web-site: <http://www.kaspersky.com> <http://www.kaspersky.com>, > <http://www.viruslist.com> <http://www.viruslist.com> > > Saludos, > Gilberto Castillo > La Habana, Cuba > > > > --- > This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running > at host imx3.etecsa.cu > > Visit our web-site: <http://www.kaspersky.com> <http://www.kaspersky.com>, > <http://www.viruslist.com> <http://www.viruslist.com> > > >
