From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Index
Date: Sun, 10 Mar 2024 12:50:13 +0100
Message-ID: <d6fb9d13-c682-cb87-804c-fd8a0ed50c84@jakobs.com> (raw)
In-Reply-To: <CAJk5AtZqnqPdoajrRM4sAEjAP=zM5d7bQ1=VY_EKJ=9vV+H+Gg@mail.gmail.com>
References: <CAJk5AtZqnqPdoajrRM4sAEjAP=zM5d7bQ1=VY_EKJ=9vV+H+Gg@mail.gmail.com>
Am 10.03.24 um 12:19 schrieb Rajesh Kumar:
> Hi ,
>
> I have a table where size is increasing daily. In that table only
> inserts and deletes happens. This table is referencing 15 other
> tables. We have given delete cascade, so if a row is deleted in parent
> table, the matching records will also be deleted in those child tables.
>
> It is taking lot of time to delete. So, I am planning to create index
> on those child tables.
>
> My question is, apart from inserts, I am only going to delete records
> from those tables. How index improves performance for deleting
> records? How index is affected or how to do index management in this case?
Hi,
Since every single row which is going to be deleted in the child tables
has to be found, an index can be of great help here.
Actually, in most (not all!) cases an index on foreign key columns makes
sense.
Regards,
Holger
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Attachments:
[application/pgp-signature] OpenPGP_signature (202B, ../d6fb9d13-c682-cb87-804c-fd8a0ed50c84@jakobs.com/2-OpenPGP_signature)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: holger@jakobs.com, pgsql-admin@lists.postgresql.org
Subject: Re: Index
In-Reply-To: <d6fb9d13-c682-cb87-804c-fd8a0ed50c84@jakobs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox