From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Carlo Stonebanks <stonec(dot)register(at)sympatico(dot)ca> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: New server to improve performance on our large and busy DB - advice? |
Date: | 2010-01-21 02:03:33 |
Message-ID: | 603c8f071001201803r3d0a1b12pd20fbc0ee71b03d5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Jan 20, 2010 at 3:03 PM, Carlo Stonebanks
<stonec(dot)register(at)sympatico(dot)ca> wrote:
>> Yes! You can run vacuum verbose against the regular old postgres
>> database (or just create one for testing with nothing in it) and
>> you'll still get the fsm usage numbers from that! So, no need to run
>> it against the big db. However, if regular vacuum verbose couldn't
>> finish in a week, then you've likely got vacuum and autovacuum set to
>> be too timid in their operation, and may be getting pretty bloated as
>> we speak. Once the fsm gets too blown out of the water, it's quicker
>> to dump and reload the whole DB than to try and fix it.
>
> My client reports this is what they actualyl do on a monthly basis.
Something is deeply wrong with your client's vacuuming policies.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2010-01-21 05:15:40 | Re: ext4 finally doing the right thing |
Previous Message | Carlo Stonebanks | 2010-01-20 22:26:05 | Re: Re: New server to improve performance on our large and busy DB - advice? (v2) |