On Mon, Aug 22, 2016 at 10:09 PM, Amit Kapila <amit.kapil...@gmail.com> wrote: > Won't the similar problem exists for nonExclusiveBackups? Basically > in similar situation, the count for nonExclusiveBackups will be > decremented and if it hits pg_start_backup_callback(), the following > Assertion can fail. > pg_start_backup_callback() > { > .. > Assert(XLogCtl->Insert.nonExclusiveBackups > 0); > .. > }
This cannot be hit for non-exclusive backups as pg_start_backup() and pg_stop_backup() need to be launched from the same session: their call will never overlap across session, and this overlap is the reason why exclusive backups are exposed to the problem. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers