On Wed, Oct 31, 2018 at 01:09:53PM -0400, Robert Haas wrote: > There's no rule whatsoever that a parallel worker can't write to the > disk. pg_start_backup and pg_stop_backup have to be > parallel-restricted because, when used in non-exclusive mode, they > establish backend-local state that wouldn't be synchronized with the > state in the workers -- namely the information that a non-exclusive > backup is in progress.
Okay, but likely we would not want to signal the postmaster unnecessarily, no? FALLBACK_PROMOTE_SIGNAL_FILE gets discarded if promotion is triggered more than once, but that does not like a sane thing to do if not necessary. As far as I understand, there has been some input on this thread: - I would prefer marking the function as parallel-restricted. - Tom would make it parallel-unsafe. - Laurenz (author of the feature) is fine with restricted or unsafe. It is a bit hard to make a decision from that :) -- Michael
signature.asc
Description: PGP signature
