Original Message
Subject: Re: [GENERAL] Synchronous Commit, WAL archiving and statement_timeout
Local Time: 3 février 2017 1:15 AM
UTC Time: 3 février 2017 00:15
From: adrian.kla...@aklaver.com
To: JP Jacoupy <jpjaco...@protonmail.com>, pgsql-general@postgresql.org
On Fri, Feb 3, 2017 at 2:15 AM, JP Jacoupy wrote:
> I expected the statement to timeout because the synchronous_commit wouldn't
> work since the Slave is down while rollbacking on the Master.
Queries being stuck because of synchronous replication are already
committed
On 02/02/2017 09:15 AM, JP Jacoupy wrote:
Hello,
I noticed something strange and I would like to understand what's
happening.
I have the following environment:
- 2 PostgreSQL instance running in hot-standby with synchronous commit
activated.
There have been many changes in replication
Hello,
I noticed something strange and I would like to understand what's happening.
I have the following environment:
- 2 PostgreSQL instance running in hot-standby with synchronous commit
activated.
(further called Master & Slave)
- The archiving of the WAL files is activated on the master