| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | obouda(at)email(dot)cz |
| Cc: | "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org, "Karsten Hilbert" <Karsten(dot)Hilbert(at)gmx(dot)net> |
| Subject: | Re: backend crash on DELETE, reproducible locally |
| Date: | 2018-11-03 19:38:14 |
| Message-ID: | 23468.1541273894@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
<obouda(at)email(dot)cz> writes:
> we reached the exactly same problem after upgrading to PostgreSQL 11 - the
> server crashed on a DELETE statement with a trigger. We also observed an
> AFTER DELETE trigger receiving NULL values in OLD. Now I see the problem
> seems to be solved (theoretically). Unfortunately, we are not able to build
> the server with the patch, so we cannot confirm that. However, when we just
> copied the database (within the same server), the same DELETE executed on
> the copy with no problems.
Yeah, dump/reload would make the problem go away.
> I would like to ask, however: could the same problem arise from an UPDATE
> statement (also on a table with an AFTER trigger), or would that be another
> bug (technical details below)?
Same bug.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Charles Martin | 2018-11-03 19:57:08 | Trouble Upgrading Postgres |
| Previous Message | obouda | 2018-11-03 19:19:19 | Re: backend crash on DELETE, reproducible locally |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2018-11-03 19:58:56 | Re: ToDo: show size of partitioned table |
| Previous Message | Tom Lane | 2018-11-03 19:35:20 | Re: plruby: rb_iterate symbol clash with libruby.so |