| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Aleksandr Parfenov <a(dot)parfenov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: PostgreSQL crashes with SIGSEGV |
| Date: | 2018-02-07 01:54:09 |
| Message-ID: | CAMsr+YHpVkKqGA-5q+JHvhSew3S4AAO_vD+aVZEXdg2NreUEDw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 18 January 2018 at 03:23, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Aleksandr Parfenov <a(dot)parfenov(at)postgrespro(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2018-02-07 01:56:25 | Re: PostgreSQL crashes with SIGSEGV |
| Previous Message | Orian Beltrame da Silva | 2018-02-06 22:44:01 | Re: BUG #15053: SIGSEGV - While executing query with cube agregator |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2018-02-07 01:56:25 | Re: PostgreSQL crashes with SIGSEGV |
| Previous Message | Kyotaro HORIGUCHI | 2018-02-07 01:34:58 | Re: [HACKERS] More stats about skipped vacuums |