Kyotaro HORIGUCHI <horiguchi.kyot...@lab.ntt.co.jp> writes:
> By the way, the reason of the "invalid snapshot identifier" is
> that some worker threads try to use it after the connection on
> the first worker closed.
... BTW, I don't quite see what the issue is there. The snapshot is
exported from the master session, so errors in worker sessions should not
cause such failures in other workers. And I don't see any such failure
when setting up a scenario that will cause a worker to fail on Linux.
The "invalid snapshot identifier" bleats would make sense if you had
gotten a server-side error (and transaction abort) in the master session,
but I don't see any evidence that that happened in that example. Might be
worth seeing if that's reproducible.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
