Re: terminated by signal 11: Segmentation fault

From: Gerrit Fouche <gerrit(dot)fouche(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: terminated by signal 11: Segmentation fault
Date: 2019-11-14 05:18:18
Message-ID: CAJGpXMi7Z10SRD6wz3EC28MOnL1h3mEYxNBRqqCw9VnpKNJwQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Tom,
Thank you, we have that same scenario.
Regards
Gerrit

On Wed, 13 Nov 2019, 20:57 Tom Lane, <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Gerrit Fouche <gerrit(dot)fouche(at)gmail(dot)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
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kyotaro Horiguchi 2019-11-14 05:28:03 Re: Wall shiping replica failed to recover database with error: invalid contrecord length 1956 at FED/38FFE208
Previous Message Adrian Klaver 2019-11-14 01:10:08 Re: ERROR: COPY escape must be a single one-byte character (multi-delimiter appears to work on Postgres 9.0 but does not on Postgres 9.2)