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 0C831D1B20D for ; Thu, 17 Jun 2004 12:58:19 -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 63200-02 for ; Thu, 17 Jun 2004 15:58:16 +0000 (GMT) Received: from fusion.bennyvision.com (fusion.bennyvision.com [216.161.119.28]) by svr1.postgresql.org (Postfix) with SMTP id 32EDAD1B1BE for ; Thu, 17 Jun 2004 12:58:14 -0300 (ADT) Received: (qmail 27369 invoked from network); 17 Jun 2004 15:58:14 -0000 Received: from localhost (HELO webmail.stinkweasel.net) (127.0.0.1) by fusion.bennyvision.com with SMTP; 17 Jun 2004 15:58:14 -0000 Received: from 134.244.169.17 (SquirrelMail authenticated user benny) by webmail.stinkweasel.net with HTTP; Thu, 17 Jun 2004 10:57:52 -0500 (CDT) Message-ID: <1854.134.244.169.17.1087487894.squirrel@webmail.stinkweasel.net> In-Reply-To: <1087486656.27839.2.camel@localhost.localdomain> 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> <1087486656.27839.2.camel@localhost.localdomain> Date: Thu, 17 Jun 2004 10:57:52 -0500 (CDT) Subject: Re: VARCHAR -vs- CHAR: huge performance difference? From: "C. Bensend" To: pgsql-admin@postgresql.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.9 tagged_above=0.0 required=5.0 tests=PRIORITY_NO_NAME, RCVD_IN_RFCI X-Spam-Level: X-Archive-Number: 200406/225 X-Sequence-Number: 13885 > 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. Hi Scott, Could you explain the fsm a little more? I have done _no_ tuning on my database simply because I don't know how, but I would be interested to hear your recommendations for the fsm settings. Thanks! Benny -- "Oh, the Jedis are going to feel this one!" -- Professor Farnsworth, "Futurama"