Re: PostgreSQL crashes with SIGSEGV - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: PostgreSQL crashes with SIGSEGV
Date
Msg-id CAMsr+YHpVkKqGA-5q+JHvhSew3S4AAO_vD+aVZEXdg2NreUEDw@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL crashes with SIGSEGV  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PostgreSQL crashes with SIGSEGV
List pgsql-hackers
On 18 January 2018 at 03:23, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Aleksandr Parfenov <a.parfenov@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

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] More stats about skipped vacuums
Next
From: Peter Geoghegan
Date:
Subject: Re: PostgreSQL crashes with SIGSEGV