Re: terminated by signal 11: Segmentation fault

Поиск
Список
Период
Сортировка
От Gerrit Fouche
Тема Re: terminated by signal 11: Segmentation fault
Дата
Msg-id CAJGpXMi7Z10SRD6wz3EC28MOnL1h3mEYxNBRqqCw9VnpKNJwQg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: terminated by signal 11: Segmentation fault  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
Hi Tom,
Thank you, we have that same scenario.
Regards
Gerrit

On Wed, 13 Nov 2019, 20:57 Tom Lane, <tgl@sss.pgh.pa.us> wrote:
Gerrit Fouche <gerrit.fouche@gmail.com> writes:
> This is the second time I get this error since Postgresql 12 was officially
> released. My version:
> PostgreSQL 12.0 (Ubuntu 12.0-2.pgdg18.04+1) on x86_64-pc-linux-gnu,
> compiled by gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0, 64-bit

Given that this failed in an UPDATE, I suspect it's a known problem:
if you have a BEFORE UPDATE row-level trigger, and a concurrent update
on the same row happens, 12.0 can dump core due to a slot memory
management mistake.  There's a fix in 12.1, due out tomorrow.

                        regards, tom lane

В списке pgsql-general по дате отправления:

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: ERROR: COPY escape must be a single one-byte character(multi-delimiter appears to work on Postgres 9.0 but does not on Postgres9.2)
Следующее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: Wall shiping replica failed to recover database with error:invalid contrecord length 1956 at FED/38FFE208