From: John Scalia <jayknowsunix@gmail.com>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Disabling indexes on a table
Date: Thu, 18 Feb 2021 11:24:57 -0500
Message-ID: <8D9636C9-D38E-4857-A542-1469A11A25FF@gmail.com> (raw)
One of my developers asked me about this, and he suggested running the following update:
UPDATE pg_index SET indisready=false
WHERE indrelid = (select oid from pg_class where release = ‘his_table’);
I told him it’s never a good idea to update anything in a system catalog by hand, but that I would reach out here for a better opinion. Am I correct that he shouldn’t try this, or is he OK to do this? His table has approximately 8 different indexes on it, and those really slow down his bulk loads. Usually when I have to get involved, I just drop his indexes and rebuild them afterwards, and I know that is always safe.
—
Jay
Sent from my iPad
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: jayknowsunix@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Disabling indexes on a table
In-Reply-To: <8D9636C9-D38E-4857-A542-1469A11A25FF@gmail.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