Michael Paquier writes:
> Andreas, with the patch attached is the assertion still triggered?
> [2. text/x-diff; base-backup-crash-v2.patch]
I didn't observe the crashes since applying this patch. There should
have been about five by the amount of fuzzing done.
regards
Andreas
--
Sent via pgs
Hello,
While the exact cause of the situation is not known yet but we
have apparently forgot that pg_stop_backup can be called
simultaneously with pg_start_backup. It seems anyway to me that
pg_stop_backup should be called before the end of pg_start_backup
from their definition and what they do. A
On Thu, Aug 4, 2016 at 4:38 PM, Michael Paquier
wrote:
> Andreas, with the patch attached is the assertion still triggered?
>
> Thoughts from others are welcome as well.
Self review:
* of streaming base backups currently in progress. forcePageWrites is set
* to true when either of the
On Thu, Aug 4, 2016 at 4:03 PM, Michael Paquier
wrote:
> This window exists as well on back-branches btw, this is not new to
> 9.6. Magnus, what do you think?
Actually, a completely water-proof solution is to use an in-memory
flag proper to exclusive backups during the time pg_start_backup() is
c
On Thu, Aug 4, 2016 at 2:19 AM, Andreas Seltenreich wrote:
> testing with sqlsmith shows that the following assertion doesn't hold:
>
> FailedAssertion("!(XLogCtl->Insert.exclusiveBackup)", File: "xlog.c",
> Line: 10200)
>
> The triggering statements always contain a call to pg_start_backup w
Hi,
testing with sqlsmith shows that the following assertion doesn't hold:
FailedAssertion("!(XLogCtl->Insert.exclusiveBackup)", File: "xlog.c", Line:
10200)
The triggering statements always contain a call to pg_start_backup with
the third argument 'true', i.e. it's trying to start an exlus
