From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jacque Edmund <jacqueedmund(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Native Foreign Keys housekeeping time intensive for Relational Model |
Date: | 2021-03-28 04:49:24 |
Message-ID: | 5d3f776063f41977df5910c6cdaef6b963342023.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sat, 2021-03-27 at 10:43 -0400, Tom Lane wrote:
> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
>
> > On Fri, 2021-03-26 at 14:00 -0400, Jacque Edmund wrote:
> > > I've already seen that my current set of FK relationships between < 100 tables and data footprint
> > > has yielded very large lookup times for the underlying referential integrity of the FKs to vet
> > > whether it can DELETE a row or not based on its FK relationships.
>
> > I would be surprised if correctly indexed foreign keys would slow deletes down so that
> > the performance becomes intolerable.
>
> Deletes being slow often means that you don't have an index on the
> referencing column(s). PG requires you to have an index on the referenced
> columns, but not on the other side of the FK relationship.
Exactly, that's what I wanted to say: I suspect that such indexes are missing
or not created correctly. Otherwise, the performance should be good.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Vivek Anandh | 2021-03-29 07:42:45 | Re: Creating redwood datestyle in Postgres 12 |
Previous Message | Tom Lane | 2021-03-27 14:43:21 | Re: Native Foreign Keys housekeeping time intensive for Relational Model |