On 4/25/17 21:47, Michael Paquier wrote:
> Attached is an updated patch to reflect that.
I edited this a bit, here is a new version.
A variant approach would be to prohibit *all* new commands after
entering the "stopping" state, just let running commands run. That way
we don't have to pick which individual commands are at risk. I'm not
sure that we have covered everything here.
More reviews please. Also, this is a possible backpatching candidate.
Also, if someone has a test script for reproducing the original issue,
please share it, or run it against this patch.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
