On 18 January 2018 at 03:23, Tom Lane <t...@sss.pgh.pa.us> wrote: > Aleksandr Parfenov <a.parfe...@postgrespro.ru> writes: > > The new status of this patch is: Ready for Committer > > I don't feel particularly comfortable committing a patch that > was clearly labeled as a rushed draft by its author. > Peter, where do you stand on this work? > > In a quick look at the patches, WIP-kludge-fix.patch seems clearly > unacceptable for back-patching because it changes the signature and > behavior of ExecResetTupleTable, which external code might well be using. >
Definitely is using, in the case of BDR and pglogical. But we can patch in a version check easily enough. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
