| From: | "K, Niranjan (NSN - IN/Bangalore)" <niranjan(dot)k(at)nsn(dot)com> |
|---|---|
| To: | "ext Fujii Masao" <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | "Kolb, Harald (NSN - DE/Munich)" <harald(dot)kolb(at)nsn(dot)com>, "Czichy, Thoralf (NSN - FI/Helsinki)" <thoralf(dot)czichy(at)nsn(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Synchronous replication: Admin command for replication_timeout_action |
| Date: | 2009-05-04 17:37:01 |
| Message-ID: | 985D3C447786074E957A9001D62CDDD05A36C1@SGSIEXC009.nsn-intra.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
This is to support an admin command or utility which can trigger the
server to be taken to a standalone mode if there a connection failure
detection between Primary and server. It need not be always, that the
replication_timeout needs to be accomplished to detect the connection
failure because it could happen that cluster/hearbeat framework might
detect the connection failure earlier to the replication_timeout. So the
admin command, which will abstract the implementation details will
assist in taking the server to standalone mode earlier to
replication_timeout.
Are there any suggestions from your side with respect to this?
regards,
Niranjan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2009-05-04 19:21:10 | Re: conditional dropping of columns/constraints |
| Previous Message | Robert Haas | 2009-05-04 17:34:41 | Re: conditional dropping of columns/constraints |