> So, if I understand correctly, then we can mark the version posted by > you upthread [1] which includes a test along with Kyotaro's fix can be > marked as Ready for committer. If so, then please change the status > of patch accordingly.
Patch moved to next CF 2016-11, still with status "ready for committer". IMO, this thread has reached as conclusion to use this patch to address the problem reported: cab7npqtv5gmkqcndofgtgqoqxz2xlz4rrw247oqojzztvy6...@mail.gmail.com -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
