Subject: [HACKERS] Multiple synchronous_standby_names rules

When working with a production (P) and a DR (D) environment it is often a requirement to be able to protect against data loss when promoting within a site, and also when losing A and promoting a master at D.
The current synchronous_standby_names do not allow this.
In a simple example we could take the following nodes:
P1 (current master), P2, P3D1, D2, D3
Where P1 is replicating to (P2, P3, D1, D2, D3).

The closest synchronous_standby_names  setting you could get to my use case would be:
1 (D1, D2, D3)
This would allow the loss of either site without losing data - however it would not allow promotion within site P from P1 -> (P2 | P3)  without the potential for data loss.
What is needed to support this is the ability to configure Px with something like:
 1 (P1, P2, P3), 1 (D1, D2, D3)
Would there be any appetite for this - or would it be seen as over complication of the current rules?

James Sewell,
PostgreSQL Team Lead / Solutions Architect 


Suite 112, Jones Bay Wharf, 26-32 Pirrama Road, Pyrmont NSW 2009
(+61) 2 8099 9000  W  F (+61) 2 8099 9099
The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender o...

f your incorrect receipt of this correspondence.

Programming list archiving by: Enterprise Git Hosting