X-Original-To: pgsql-performance@postgresql.org Received: from joeconway.com (66-146-172-86.skyriver.net [66.146.172.86]) by postgresql.org (Postfix) with ESMTP id AEDF8476358 for ; Wed, 12 Mar 2003 21:00:08 -0500 (EST) Received: from [192.168.5.3] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 4.0.4) with ESMTP-TLS id 1662409; Wed, 12 Mar 2003 18:36:03 -0800 Message-ID: <3E6FE59E.1050602@joeconway.com> Date: Wed, 12 Mar 2003 17:57:50 -0800 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Max Baker Cc: Manfred Koizar , PostgreSQL Performance Mailing List Subject: Re: speeding up COUNT and DISTINCT queries References: <20030312223811.GM30411@warped.org> <20030313015540.GP30411@warped.org> In-Reply-To: <20030313015540.GP30411@warped.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/91 X-Sequence-Number: 1389 Max Baker wrote: > Thanks for the help. I guess i'm not clear on why there is so much > extra cruft. Does postgres leave a little bit behind every time it does > an update? Because this table is updated constantly. > Yes. See: http://www.us.postgresql.org/users-lounge/docs/7.3/postgres/routine-vacuuming.html Joe