Re: Bad performance with cascaded deletes

2018-06-12 Thread Don Seiler
On Tue, Jun 12, 2018 at 10:48 AM, Don Seiler wrote: > On Tue, Jun 12, 2018 at 2:26 AM, Haug Bürger > wrote: > >> >> "availability_cache_ac_session_id_fkey" FOREIGN KEY (ac_session_id) >> REFERENCES zpg_data.session(id) ON DELETE CASCADE >> >> > Do you have an index on availability_cache.ac_s

Re: Bad performance with cascaded deletes

2018-06-12 Thread Don Seiler
On Tue, Jun 12, 2018 at 2:26 AM, Haug Bürger wrote: > > "availability_cache_ac_session_id_fkey" FOREIGN KEY (ac_session_id) > REFERENCES zpg_data.session(id) ON DELETE CASCADE > > Do you have an index on availability_cache.ac_session_id? These fields are not automatically indexed and that can

Re: Bad performance with cascaded deletes

2018-06-12 Thread Laurenz Albe
Haug Bürger wrote: > Delete on zpg_data.session (cost=190.51..4491.20 rows=500 width=46) > ... > Planning time: 0.222 ms > Trigger RI_ConstraintTrigger_a_16481 for constraint > availability_cache_ac_session_id_fkey: time=350.116 calls=500 > > For me this reads like the delete takes 0.2ms and the