On 5/5/17 01:26, Michael Paquier wrote: > The only code path doing HOT-pruning and generating WAL is > heap_page_prune(). Do you think that we need to worry about FPWs as > well? > > Attached is an updated patch, which also forbids the run of any > replication commands when the stopping state is reached.
I have committed this without the HOT pruning change. That can be considered separately, and I think it could use another round of thinking about it. I will move the open item to "Older Bugs" now, because the user experience regression, so to speak, in version 10 has been addressed. (This could be a backpatching candidate, but I am not planning on it for next week's releases in any case.) -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers