Re: backend crash on DELETE, reproducible locally

From: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: backend crash on DELETE, reproducible locally
Date: 2018-11-01 14:42:57
Message-ID: 20181101144257.GD2954@hermes.hilbert.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


> I am running this delete statement via psql
>
> DELETE FROM ref.auto_hint WHERE title = 'Kontraindikation: ACE/Sartan <-> Schwangerschaft';
>
> and it crashes the backend it is running on.

For what it is worth I have identified the physical file

gnumed_v21=# select pg_relation_filepath('ref.auto_hint');
pg_relation_filepath
----------------------
base/139580/111088
(1 Zeile)

and phyically copied that to another place (so there's no
read error on the disk - but the DELETE would perhaps ask for
a physical write test ?).

Attached the output of pg_filedump which, to me, doesn't seem
to show anything out of the ordinary either.

Corrupt index should not be the case because the databse is
REINDEXed during the upgrade process before the failing
statement.

Will attempt to get a stack trace ...

Thanks,
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B

Attachment Content-Type Size
111088_fsm.pg_filedump-v-f-i-k.txt text/plain 2.1 KB
111088.pg_filedump-v-f-i-k.txt text/plain 52.9 KB

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karsten Hilbert 2018-11-01 15:11:33 Re: backend crash on DELETE, reproducible locally
Previous Message Tom Lane 2018-11-01 14:35:40 Re: backend crash on DELETE, reproducible locally

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-11-01 14:43:58 Re: POC: Cleaning up orphaned files using undo logs
Previous Message Daniel Gustafsson 2018-11-01 14:40:59 Re: PG vs macOS Mojave