| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Aleksandr Parfenov <a(dot)parfenov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL crashes with SIGSEGV |
| Date: | 2018-02-07 01:56:25 |
| Message-ID: | CAH2-Wzkh3rgJhpfVv9faFtbzgPae2z8z+oGsYSjD1Gg8S4jauA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Tue, Feb 6, 2018 at 5:54 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>> 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.
That won't be necessary. The WIP-kludge-fix.patch approach is never
going to be used, and was only really posted for illustrative
purposes.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Seungmin Lucas Yoo | 2018-02-07 10:27:20 | About error in pgadmin when making server |
| Previous Message | Craig Ringer | 2018-02-07 01:54:09 | Re: PostgreSQL crashes with SIGSEGV |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2018-02-07 02:00:49 | Re: Query running for very long time (server hanged) with parallel append |
| Previous Message | Craig Ringer | 2018-02-07 01:54:09 | Re: PostgreSQL crashes with SIGSEGV |