Kevin Grittner schrieb am 29.07.2015 um 23:10:
No, it means that if the primary is hit by a meteor and you promote
the standby, the data will not have been lost. The time between
the successful return of the commit on the primary and the time at
which the change becomes visible on the standby is
On 07/29/2015 02:27 PM, Ravi Krishna wrote:
"Not necessarily. There has been discussion of adding a new mode
which will delay the commit on the primary until it is visible on a
synchronous standby, but I don't recall where that left off. "
Joshua: THis essentially contradicts your statement
"Not necessarily. There has been discussion of adding a new mode
which will delay the commit on the primary until it is visible on a
synchronous standby, but I don't recall where that left off. "
Joshua: THis essentially contradicts your statement to me.
On Wed, Jul 29, 2015 at 5:10 PM, Kevin
Ravi Krishna wrote:
> As per this:
>
> http://www.postgresql.org/docs/current/static/warm-standby.html#SYNCHRONOUS-REPLICATION
>
> "When requesting synchronous replication, each commit of a write
> transaction will wait until confirmation is received that the commit
> has been written to the tran
> Chris/Joshua
>
> I would like to know more details.
>
> As per this:
>
> http://www.postgresql.org/docs/current/static/warm-standby.html#SYNCHRONOUS-REPLICATION
>
> "When requesting synchronous replication, each commit of a write
> transaction will wait until confirmation is received that the
Chris/Joshua
I would like to know more details.
As per this:
http://www.postgresql.org/docs/current/static/warm-standby.html#SYNCHRONOUS-REPLICATION
"When requesting synchronous replication, each commit of a write
transaction will wait until confirmation is received that the commit
has been wri
> Does sync replication guarantee that any inserted data on primary is
> immediately visible for read on standbys with no lag.
Basically yes. Of course there is *some* latency, at the very least
from the network.
If I run a process on a standby machine that displays a value every
0.1 sec and upda
Does sync replication guarantee that any inserted data on primary is
immediately visible for read on standbys with no lag.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
