Re: Postgresql 'eats' all mi data partition

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Szepe <szepe(at)pinerecords(dot)com>
Cc: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, Javier Carlos <fjcarlos(at)correo(dot)insp(dot)mx>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Postgresql 'eats' all mi data partition
Date: 2003-09-26 18:31:08
Message-ID: 25434.1064601068@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tomas Szepe <szepe(at)pinerecords(dot)com> writes:
> We have a production database that happens to receive several
> thousand row updates per minute. We VACUUM ANALYZE every four
> hours with max_fsm_pages set to 2100000, and it's no use.

Have you spent any time determining exactly where the problem is?
I'm suspicious that it's an index-bloat issue.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomas Szepe 2003-09-26 18:43:29 Re: Postgresql 'eats' all mi data partition
Previous Message Stephan Szabo 2003-09-26 18:25:15 Re: Postgresql 'eats' all mi data partition