Re: Synchronous Standalone Master Redoux

From: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
To: "'Jose Ildefonso Camargo Tolosa'" <ildefonso(dot)camargo(at)gmail(dot)com>, <sthomas(at)optionshouse(dot)com>
Cc: "'Daniel Farina'" <daniel(at)heroku(dot)com>, "'Dimitri Fontaine'" <dimitri(at)2ndquadrant(dot)fr>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Synchronous Standalone Master Redoux
Date: 2012-07-12 06:03:26
Message-ID: 001c01cd5ff4$0e2e80c0$2a8b8240$@kapila@huawei.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> From: pgsql-hackers-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-owner(at)postgresql(dot)org]
> On Behalf Of Jose Ildefonso Camargo Tolosa

> Please, stop arguing on all of this: I don't think that adding an
> option will hurt anybody (specially because the work was already done
> by someone), we are not asking to change how the things work, we just
> want an option to decided whether we want it to freeze on standby
> disconnection, or if we want it to continue automatically... is that
> asking so much?

I think this kind of decision should be done from outside utility or
scripts.
It would be better if from outside it can be detected that stand-by is down
during sync replication, and send command to master to change its mode or
change settings appropriately without stopping master.
Putting this kind of more and more logic into replication code will make it
more cumbersome.

With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Farina 2012-07-12 06:12:35 Re: DELETE vs TRUNCATE explanation
Previous Message Tom Lane 2012-07-12 05:40:57 Re: has_language_privilege returns incorrect answer for non-superuser