Re: Postgresql performance in production environment

From: "Phoenix Kiula" <phoenix(dot)kiula(at)gmail(dot)com>
To: "Magnus Hagander" <magnus(at)hagander(dot)net>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Postgresql performance in production environment
Date: 2007-08-19 12:21:44
Message-ID: e373d31e0708190521o6f113812k92ad70029eef7cd2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 19/08/07, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> Phoenix Kiula wrote:
> > On 19/08/07, Magnus Hagander <magnus(at)hagander(dot)net> wrote:

> > should we do one (VACUUM FULL) now given that we've overrun our max_fsm_pages?
>
> Yes, but not until you've fixed it. And only once.
>

FIxed what - the max_fsm_pages? That was my question: how to know what
value to set for this. If the "vacuum verbose" won't give me the info
you suggested because it is likely overlapping with autovacuum, should
I temporarily turn autovacuum off and then run vacuum verbose? Also,
while running vacuum full, any precautions to take?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bill Moran 2007-08-19 12:23:49 Re: Seeking datacenter PITR backup procedures [RESENDING]
Previous Message Karsten Hilbert 2007-08-19 12:19:02 Re: SUBSTRING performance for large BYTEA