Following design offers simplicity of design, performance and user
control over sync rep waits, including wait-for-apply for HS.
This implements Oracle's Maximum Availability option AND Maximum
Performance options both together, rather than just one or the other:
async and sync replication
On Thu, May 27, 2010 at 9:08 AM, Simon Riggs si...@2ndquadrant.com wrote:
* New process: WALAck (on standby)
Reads shared memory to get last received and last applied xlog location
and sends message to WALSync on primary. Loop/Sleep forever.
So would WALAck be polling shared memory? That
On Thu, 2010-05-27 at 10:11 -0400, Robert Haas wrote:
On Thu, May 27, 2010 at 9:08 AM, Simon Riggs si...@2ndquadrant.com wrote:
* New process: WALAck (on standby)
Reads shared memory to get last received and last applied xlog location
and sends message to WALSync on primary. Loop/Sleep
On Thu, May 27, 2010 at 11:50 AM, Simon Riggs si...@2ndquadrant.com wrote:
On Thu, 2010-05-27 at 10:11 -0400, Robert Haas wrote:
On Thu, May 27, 2010 at 9:08 AM, Simon Riggs si...@2ndquadrant.com wrote:
* New process: WALAck (on standby)
Reads shared memory to get last received and last
