Query Performance after pg_restore

Поиск
Список
Период
Сортировка
От Murthy Nunna
Тема Query Performance after pg_restore
Дата
Msg-id DM8PR09MB66777254DC04045815B09196B89AA@DM8PR09MB6677.namprd09.prod.outlook.com
обсуждение исходный текст
Ответы Re: Query Performance after pg_restore  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Query Performance after pg_restore  (Laurenz Albe <laurenz.albe@cybertec.at>)
Список 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!

 

 

 

В списке pgsql-admin по дате отправления:

Предыдущее
От: Murthy Nunna
Дата:
Сообщение: RE: Timestamps in outputs
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Query Performance after pg_restore