pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew T. O'Connor <matthew@zeut.net>
To: Gábriel Ákos <akos.gabriel@i-logic.hu>
Cc: pgsql-performance@postgresql.org
Subject: Re: count(*) performance
Date: Mon, 27 Mar 2006 14:21:38 -0500
Message-ID: <44283B42.7060803@zeut.net> (raw)
In-Reply-To: <44282D45.7020008@i-logic.hu>
References: <C04D6B95.20285%llonergan@greenplum.com>
	<44282D45.7020008@i-logic.hu>

Gábriel Ákos wrote:
> Luke Lonergan wrote:
>> Gabriel,
>>
>> On 3/27/06 10:05 AM, "Gábriel Ákos" <akos.gabriel@i-logic.hu> wrote:
>>
>>> That gave me an idea. I thought that autovacuum is doing it right, but I
>>> issued a vacuum full analyze verbose , and it worked all the day.
>>> After that I've tweaked memory settings a bit too (more fsm_pages)
>>
>> Oops! I replied to your disk speed before I saw this.
>>
>> The only thing is - you probably don't want to do a "vacuum full", but
>> rather a simple "vacuum" should be enough.
> 
> I thought that too. Autovacuum is running on our system but it didn't do 
> the trick. Anyway the issue is solved, thank you all for helping. :)

Yeah, it would be nice of autovacuum had some way of raising a flag to 
the admin that given current settings (thresholds, FSM etc...), it's not 
keeping up with the activity.  I don't know how to do this, but I hope 
someone else has some good ideas.

Matt




view thread (17+ messages)  latest in thread

Message-ID: <44283B42.7060803@zeut.net>
Permalink:  ../44283B42.7060803@zeut.net/
Also on:    postgresql.org/message-id/44283B42.7060803@zeut.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: matthew@zeut.net, akos.gabriel@i-logic.hu
  Subject: Re: count(*) performance
  In-Reply-To: <44283B42.7060803@zeut.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox