Re: PostgreSQL crashes with SIGSEGV
| От | Craig Ringer |
|---|---|
| Тема | Re: PostgreSQL crashes with SIGSEGV |
| Дата | |
| Msg-id | CAMsr+YHpVkKqGA-5q+JHvhSew3S4AAO_vD+aVZEXdg2NreUEDw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: PostgreSQL crashes with SIGSEGV (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: PostgreSQL crashes with SIGSEGV
|
| Список | 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.
В списке pgsql-hackers по дате отправления: