From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: namdevrahul@gmail.com
Subject: BUG #16907: Performance issue after big table drop and recreate
Date: Mon, 01 Mar 2021 12:15:41 +0000
Message-ID: <16907-5d18e09e080a1bba@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16907
Logged by: Rahul Namdeo
Email address: namdevrahul@gmail.com
PostgreSQL version: 10.15
Operating system: NAME="Ubuntu" VERSION="18.04.3 LTS (Bionic Beaver)
Description:
1. Took pg_dump of 580 GB table with no data.
2. Rename the original table to TABLE1_original
3. Dropped the five indexes approx 1.2 TB on this table.
4. Did a pg_restore from the backup taken.
5. Created the indexes / constraints and provided all the grants as
required.
6 Run the Application process for report generation. It took 25 mins for
single day report which was expected behavior.
7. However after 3-4 days run the performance was degraded and the same
report now takes 2.5 Hours.
Any help will be appreciated. Kindly support.
NOTE: the Environment is on AWS Cloud Server is M5.4xLarge (16 Core 61 GB)
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, namdevrahul@gmail.com
Subject: Re: BUG #16907: Performance issue after big table drop and recreate
In-Reply-To: <16907-5d18e09e080a1bba@postgresql.org>
* 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