Re: pg_dump 3 times as slow after 8.4 -> 9.5 upgrade
От | Henrik Cednert (Filmlance) |
---|---|
Тема | Re: pg_dump 3 times as slow after 8.4 -> 9.5 upgrade |
Дата | |
Msg-id | 540BF7AC-F405-4DE5-9B58-5DC2E70F3B68@filmlance.se обсуждение исходный текст |
Ответ на | RE: pg_dump 3 times as slow after 8.4 -> 9.5 upgrade (Igor Neyman <ineyman@perceptron.com>) |
Ответы |
RE: pg_dump 3 times as slow after 8.4 -> 9.5 upgrade
|
Список | pgsql-performance |
I VACUUM every sunday so that is done already. =/
--
Henrik Cednert
cto | compositor
Filmlance International
mobile [ + 46 (0)704 71 89 54 ]
skype [ cednert ]
Not sure I have the proper params though since I'm not used to db's but have followed other's "how to's", but these are the lines in my script for that;
${BINARY_PATH}/vacuumdb --analyze --host=localhost --username=postgres --echo --verbose --no-password ${database} | tee -a ${log_pg_optimize}_${database}.log
${BINARY_PATH}/reindexdb --host=localhost --username=postgres --no-password --echo ${database} | tee -a ${log_pg_optimize}_${database}.log
--
Henrik Cednert
cto | compositor
Filmlance International
mobile [ + 46 (0)704 71 89 54 ]
skype [ cednert ]
On 21 Nov 2017, at 17:44, Igor Neyman <ineyman@perceptron.com> wrote:From: Henrik Cednert (Filmlance) [mailto:henrik.cednert@filmlance.se]
Sent: Tuesday, November 21, 2017 11:37 AM
To: pgsql-performance@lists.postgresql.org
Subject: Re: pg_dump 3 times as slow after 8.4 -> 9.5 upgradeAttention: This email was sent from someone outside of Perceptron. Always exercise caution when opening attachments or clicking links from unknown senders or when receiving unexpected emails.
RAID6. Doing disk test I have 1000MB/sec write and 1200MB/sec read.
--
Henrik Cednert
cto | compositor
Filmlance International
mobile [ + 46 (0)704 71 89 54 ]
skype [ cednert ]
_________________________________________________________________________________________________Okay, I was kind of wrong about 40GB. That’s the size of your compressed backup files, not the size of your databases.May be your dbs are “bloated”?You could try VACUUM FULL on your databases, when there is no other activity.Igor Neyman
В списке pgsql-performance по дате отправления: