From: Tom Lane <tgl@sss.pgh.pa.us>
To: tejaschavanr10@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16904: Dropping and recreating a large table with 5 indexes slowed down query performance
Date: Mon, 01 Mar 2021 09:40:07 -0500
Message-ID: <715949.1614609607@sss.pgh.pa.us> (raw)
In-Reply-To: <16904-a93be8f06fa8c49b@postgresql.org>
References: <16904-a93be8f06fa8c49b@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> The steps performed are as below:
> - Renamed the original table as _bkp
> - Dropped indexes and constraints on the backup table
> - Created the original table along with indexes with the same index name as
> before
> Post performing this activity, the queries which where performing well
> before are running very slow.
Perhaps ANALYZE'ing the new table would help. I'd have expected
autovacuum to do that for you by now, but maybe it's not able to
complete for some reason.
regards, tom lane
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, tejaschavanr10@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16904: Dropping and recreating a large table with 5 indexes slowed down query performance
In-Reply-To: <715949.1614609607@sss.pgh.pa.us>
* 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