From: | bricklen <bricklen(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Vacuum duration + hint bits? |
Date: | 2009-08-27 23:02:15 |
Message-ID: | 33b743250908271602v57e13ec3y4fc74a0727998bc5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi, I have a question about a db-wide vacuum that I am running that is
taking a much longer time than normal. We switched over to our warm standby
server today -- which is virtually identical to the source db server -- and
I initiated a "vacuum analyze verbose". Normally this process wouldn't take
more than 6 hours, but so far we are well over 9 hours. I seem to recall
reading in one of these pg lists that a db-wide vacuum of a new (?) database
would go about setting the hint bits and cause a lot more disk IO than is
normal. Is that a possible cause.
Postgresql 8.2.13, RHEL5
Sorry, I realize I'm short on details, but I'm just running out the door and
the thought about hint bits struck me.
Cheers!
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-08-27 23:05:26 | Re: Vacuum duration + hint bits? |
Previous Message | Greg Smith | 2009-08-27 22:57:47 | Re: Performance issues with large amounts of time-series data |