From: Tom Lane <tgl@sss.pgh.pa.us>
To: Aleksandr Parfenov <a.parfenov@postgrespro.ru>
Cc: pgsql-hackers@lists.postgresql.org, Peter Geoghegan <pg@bowt.ie>
Subject: Re: PostgreSQL crashes with SIGSEGV
Date: Wed, 17 Jan 2018 14:23:18 -0500
Message-ID: <14267.1516216998@sss.pgh.pa.us> (raw)
In-Reply-To: <151608914608.25640.2144132915573008595.pgcf@coridan.postgresql.org>
References: <1512661638.9720.34.camel@oopsware.de>
<CAH2-WzmxBVYUrqtmOyP9jB1j2ZO7xTpPx65ZKTO362Qg0MRgxA@mail.gmail.com>
<151608914608.25640.2144132915573008595.pgcf@coridan.postgresql.org>
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.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, a.parfenov@postgrespro.ru, pg@bowt.ie
Subject: Re: PostgreSQL crashes with SIGSEGV
In-Reply-To: <14267.1516216998@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox