Sure you're right... my oversight, sorry. I wanted only to create a
situation in which the standby remains quite behind with updates, so we
can suppose that there is a list of standby servers (so the primary
keeps going on with the 2nd) or simply suppose the replication async.
Pupillo
Il 25/10
I may be confused but...
On Tue, Oct 25, 2016 at 5:08 PM, t.dalpo...@gmail.com
wrote:
> These servers are configured for Sync streaming replication .
> Let's suppose that the standby stays down for a long time, then it restarts,
Doesn't sync replication plus standby down mean primary will stop
a
On Tuesday 25 October 2016 17:08:26 t.dalpo...@gmail.com wrote:
> Hi,
> let's suppose I have:
> - a primary server with its own local archive location, configured for
> continuous archiving
> - a standby server without archive.
> These servers are configured for Sync streaming replication .
> L
Hi,
let's suppose I have:
- a primary server with its own local archive location, configured for
continuous archiving
- a standby server without archive.
These servers are configured for Sync streaming replication .
Let's suppose that the standby stays down for a long time, then it
restarts,
On Mon, 25 Nov 2013, Tree wrote:
TLDR: We want to be able to use streaming replication, WAL archiving, and
have the ability to restore from a backup made before a failover using the
WAL archive.
(cutting rest of long description)
So, is it possible to use a "long-term WAL archive area" (as t
TLDR: We want to be able to use streaming replication, WAL archiving, and
have the ability to restore from a backup made before a failover using the
WAL archive.
Setup:
We use postgresql 9.1 with streaming replication between a pair of nodes.
The nodes are identical, and can fail over and fa
