Skip site navigation (1) Skip section navigation (2)

Re: VARCHAR -vs- CHAR: huge performance difference?

From: "Scott Marlowe" <smarlowe(at)qwest(dot)net>
To: "Olivier Hubaut" <olivier(at)scmbb(dot)ulb(dot)ac(dot)be>
Cc: "C(dot) Bensend" <benny(at)bennyvision(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: VARCHAR -vs- CHAR: huge performance difference?
Date: 2004-06-17 15:37:36
Message-ID: 1087486656.27839.2.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-admin
On Thu, 2004-06-17 at 00:46, Olivier Hubaut wrote:
> On Wed, 16 Jun 2004 09:37:58 -0500 (CDT), C. Bensend  
> <benny(at)bennyvision(dot)com> wrote:
> 
> >
> >> You might want to look into the autovacuum daemon, and / or increasing
> >> fsm settings to be large enough to hold all the spare tuples released by
> >> vacuuming.
> >
> > IIRC, the autovacuum stuff was added in 7.4, which I'm not running (yet).
> > An upgrade to 7.4.3 might be prudent for me, while the database is still
> > small.
> >
> > Benny
> >
> >
> 
> By the way, be carefull. The pg_autovacuum is not good enough for being  
> using as the only way for cleaning the database, especially if you have a  
> lot of update and delete on the same tables.

The problem here isn't pg_autovacuum, but too small of settings for
fsm.  I've run multi-day tests where autovacuum kept the size of the
database pretty much the same with 200+ updates a second going on.


In response to

Responses

pgsql-admin by date

Next:From: C. BensendDate: 2004-06-17 15:57:52
Subject: Re: VARCHAR -vs- CHAR: huge performance difference?
Previous:From: C. BensendDate: 2004-06-17 14:58:52
Subject: Re: VARCHAR -vs- CHAR: huge performance difference?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group