> Definitely look at updating to the latest 8.2 release, there's a lot of
bug fixes since 8.2.3.
Yes, we're planning out to upgrade the version.
> Usually I set max_fsm_pages to 2x or more whatever vacuum verbose says it
needs.
A snippet of my VACUUM ANALYZE VERBOSE is pasted below. To set this
p
On Sat, Jul 31, 2010 at 1:00 AM, Gnanakumar wrote:
> Hi Scott,
>
> Thanks for your valuable suggestion. Our production server is running
> PostgreSQL 8.2.3 on Red Hat 4.1.1-52.
Definitely look at updating to the latest 8.2 release, there's a lot
of bug fixes since 8.2.3.
>
>> Esp in 8.3 and be
Hi Scott,
Thanks for your valuable suggestion. Our production server is running
PostgreSQL 8.2.3 on Red Hat 4.1.1-52.
> Esp in 8.3 and before where blowing out the free space map is quite easy
to do and it can go unnoticed for some time.
As you pointed out rightly, recently in our Production s
On Fri, Jul 30, 2010 at 11:18 PM, Gnanakumar wrote:
> Hi,
>
> What are all the controlling factors/measures that one should consider/take
> into account, when there is an unexpected growth in disk space usage of the
> database?
>
> Some of the factors that comes to my mind immediately are:
> 1) Ru
Hi,
What are all the controlling factors/measures that one should consider/take
into account, when there is an unexpected growth in disk space usage of the
database?
Some of the factors that comes to my mind immediately are:
1) Running autovacuum daemon aggressively
2) Setting/tuning appropriate
