Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 80CFA64FF27 for ; Mon, 21 Jul 2008 08:32:45 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 74990-01 for ; Mon, 21 Jul 2008 08:32:37 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by postgresql.org (Postfix) with ESMTP id C568364FCDC for ; Mon, 21 Jul 2008 08:32:39 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id d37so755216pye.29 for ; Mon, 21 Jul 2008 04:32:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=gxLzjfX0CntR9CUIJav5sGfx0KEVPre8Z+klMGIW3og=; b=x6mGCRRKqCPp9qz+gt+KXoJYgHQfQNh6vekXlHzvPV+1nghEVjgdYM7CB+3IPuKEyi EBw9xHqif+bTUDO9c+HaE2+dp05DWP2S4N+IxOT7Tg0sHUkxTf6bh+TtwCNrlCsy8G5u LWIC0ZwuodXDpldnq9FKuiH/mHjhDJzCr+DWg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=PfL/MDJ6AdYL59Xxjcv0QE4M/sDuOqIuQ8bvsnygsdR5E42O0vcgwwp0m1l5h8FwHV cU2tBScWbQ4muBQ4UTGwLAEXMUjA+NdaMmXKnE2r3jm0MJIavXQn3je1CuVExOUDi6KJ tJt4HOT7dgh9wzoHjG5uMAP6yD2hpAR0UASJE= Received: by 10.142.218.4 with SMTP id q4mr1282051wfg.262.1216639957797; Mon, 21 Jul 2008 04:32:37 -0700 (PDT) Received: by 10.142.188.15 with HTTP; Mon, 21 Jul 2008 04:32:37 -0700 (PDT) Message-ID: <1d4e0c10807210432v45c6272awb1ea13974747de54@mail.gmail.com> Date: Mon, 21 Jul 2008 13:32:37 +0200 From: "Guillaume Smet" To: "Andreas Hartmann" Subject: Re: Less rows -> better performance? Cc: pgsql-performance@postgresql.org In-Reply-To: <4884722A.1000405@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48846A02.7090702@apache.org> <48846DA3.2090308@archonet.com> <4884722A.1000405@apache.org> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200807/176 X-Sequence-Number: 30776 On Mon, Jul 21, 2008 at 1:25 PM, Andreas Hartmann wrote: > SELECT pg_database.datname, > pg_size_pretty(pg_database_size(pg_database.datname)) AS size > FROM pg_database where pg_database.datname = 'vvz_live_1'; > > datname | size > ---------------+--------- > vvz_live_1 | 2565 MB > > I wonder why the actual size is so much bigger than the data-only dump - is > this because of index data etc.? More probably because the database is totally bloated. Do you run VACUUM regularly or did you set up autovacuum? -- Guillaume