| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ondřej Bouda <obouda(at)email(dot)cz> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Ondřej Bouda <bouda(at)edookit(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-06 19:49:44 |
| Message-ID: | 31911.1541533784@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
=?UTF-8?Q?Ond=c5=99ej_Bouda?= <obouda(at)email(dot)cz> writes:
> I thought triggers should be suspected. However, even when all the three
> triggers have been disabled (ALTER TABLE DISABLE TRIGGER), the UPDATE
> crashed the server.
Foreign-key triggers too?
> What else could I try?
A stack trace would be really helpful.
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ondřej Bouda | 2018-11-06 19:54:31 | Re: backend crash on DELETE, reproducible locally |
| Previous Message | Condor | 2018-11-06 19:49:17 | Re: Question about index on different tablespace and rebuild it |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ondřej Bouda | 2018-11-06 19:54:31 | Re: backend crash on DELETE, reproducible locally |
| Previous Message | Isaac Morland | 2018-11-06 19:46:28 | Re: Disallow setting client_min_messages > ERROR? |