X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id CAD1CD1B1CD for ; Thu, 17 Jun 2004 12:36:55 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 31813-05 for ; Thu, 17 Jun 2004 15:36:54 +0000 (GMT) Received: from mpls-qmqp-03.inet.qwest.net (mpls-qmqp-03.inet.qwest.net [63.231.195.114]) by svr1.postgresql.org (Postfix) with SMTP id 04ADDD1B20D for ; Thu, 17 Jun 2004 12:36:51 -0300 (ADT) Received: (qmail 2572 invoked by uid 0); 17 Jun 2004 15:08:18 -0000 Received: from mpls-pop-07.inet.qwest.net (63.231.195.7) by mpls-qmqp-03.inet.qwest.net with QMQP; 17 Jun 2004 15:08:18 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-07.inet.qwest.net with SMTP; 17 Jun 2004 15:36:50 -0000 Date: Thu, 17 Jun 2004 09:37:36 -0600 Message-Id: <1087486656.27839.2.camel@localhost.localdomain> From: "Scott Marlowe" To: "Olivier Hubaut" Cc: "C. Bensend" , pgsql-admin@postgresql.org Subject: Re: VARCHAR -vs- CHAR: huge performance difference? In-Reply-To: References: <51429.63.227.74.41.1087347504.squirrel@webmail.stinkweasel.net> <15549.1087351669@sss.pgh.pa.us> <50124.63.227.74.41.1087351971.squirrel@webmail.stinkweasel.net> <15996.1087354312@sss.pgh.pa.us> <58063.63.227.74.41.1087355391.squirrel@webmail.stinkweasel.net> <1087363871.1582.20.camel@localhost.localdomain> <1185.134.244.169.17.1087396700.squirrel@webmail.stinkweasel.net> Content-Type: text/plain Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/224 X-Sequence-Number: 13884 On Thu, 2004-06-17 at 00:46, Olivier Hubaut wrote: > On Wed, 16 Jun 2004 09:37:58 -0500 (CDT), C. Bensend > 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.