Query Performance after pg_restore

From: Murthy Nunna <mnunna(at)fnal(dot)gov>
To: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Query Performance after pg_restore
Date: 2023-12-24 15:53:39
Message-ID: DM8PR09MB66777254DC04045815B09196B89AA@DM8PR09MB6677.namprd09.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi,

I did pg_dump of a ~20TB database followed by pg_restore. I find simple queries like select count(*) running slow. I did a select count(*) on all tables before pg_dump which took ~4 hours. After pg_restore, same thing took 32 hours.

I ran "analyze verbose ;" on the database, but it did not help. It ran quick in 1.5 hours, but as you are aware it does sampling.

I am now running "vacuumdb -p <port-number> -a -z -j 10 -v", but I do not know if it is going to help.

I am not sure if above vacuumdb helps, but if it helps what is it vacuuming in a pristine database? If it is doing some special "analyze", what is it? Is there a way to run "full" analyze without sampling and without vacuuming?

By the way, there is no change in postgres versions. It is 14.4 before and after pg_restore.

Thanks!

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2023-12-24 16:12:15 Re: Query Performance after pg_restore
Previous Message Murthy Nunna 2023-12-24 15:36:27 RE: Timestamps in outputs