Re: Bad performance with cascaded deletes - Mailing list pgsql-general

From Don Seiler
Subject Re: Bad performance with cascaded deletes
Date
Msg-id CAHJZqBDvkLTyESVrTGXOX0Tz7rTj=WNdhUGr9dGiu3pa7YmQZw@mail.gmail.com
Whole thread Raw
In response to Re: Bad performance with cascaded deletes  (Don Seiler <don@seiler.us>)
List pgsql-general
On Tue, Jun 12, 2018 at 10:48 AM, Don Seiler <don@seiler.us> wrote:
On Tue, Jun 12, 2018 at 2:26 AM, Haug Bürger <haug.buerger@zalando.de> 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 lead to horrible performance on cascading operations like this.

I'm blind apparently, it's your PK. 

--
Don Seiler
www.seiler.us

pgsql-general by date:

Previous
From: Don Seiler
Date:
Subject: Re: Bad performance with cascaded deletes
Next
From: Scott Stroupe
Date:
Subject: Print pg_lsn as a number?