Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 4205B1337B69 for ; Mon, 4 Apr 2011 13:23:53 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 48970-03 for ; Mon, 4 Apr 2011 16:23:43 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from nm18-vm0.bullet.mail.ukl.yahoo.com (nm18-vm0.bullet.mail.ukl.yahoo.com [217.146.183.95]) by mail.postgresql.org (Postfix) with SMTP id 5A2061337B43 for ; Mon, 4 Apr 2011 13:23:41 -0300 (ADT) Received: from [217.146.183.213] by nm18.bullet.mail.ukl.yahoo.com with NNFMP; 04 Apr 2011 16:23:40 -0000 Received: from [217.146.183.175] by tm6.bullet.mail.ukl.yahoo.com with NNFMP; 04 Apr 2011 16:23:40 -0000 Received: from [127.0.0.1] by omp1016.mail.ukl.yahoo.com with NNFMP; 04 Apr 2011 16:23:40 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 947469.59698.bm@omp1016.mail.ukl.yahoo.com Received: (qmail 75180 invoked by uid 60001); 4 Apr 2011 16:23:40 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1301934220; bh=ouxRLmeZ+PchqiHo8erfABGc4wFaOaTujos6kRdQfnE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=m90KJct85hr1dvbnE7k9ZGdJHF+T4c7aPXwRSdFfgLQA95fe8opJfnNSx4gkCnOWF9Pb/buHO1xBiS2U4tn2TYrJCDlj08EQuUKV/xBxsIOPi5d+to34ilzhiHvcVYs8tC5A4KaM5jUAwxi5UCoC6NYlpM8QDahNkFcXjgU6LPU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=q/mGo4BBNaLIxMm/8X/EsPbbiqa1tM34yA5v3kA2AiIzp6fdWiCuAY9m7lvgeXAqqFpQ1TD0wQRM4cqEiFr52S2ZadJxmwQLG4HF2EIIaMReOkRd0fGdDuUbSJUq8Ked4pcAfvct928J1hIuDapeeJmJOPatTcxCM/7f+oZ9wlY=; Message-ID: <736208.74368.qm@web26007.mail.ukl.yahoo.com> X-YMail-OSG: mxl0Ax8VM1mi5M_MW.MyFKd42bxQBRHgPe.24HiW6BerJoB _lQ.s8KojO5x4rPnehE1pyHH1a82a5X1v9Oe8Z4ywi1M7avPVpMDMf4w7YHb MbMSEXvzDthW6SD6ufec1GXjnBWoUeHiYBQPEH79eX9mnggD4shoHR10NM9M myf6yLkmQ3HAJs32TPElYFdhTsB4bN7ygNMoGtfnPcmhBk0XmShwSDYwWfl5 Wo_GlrOr568wFasyBzcF.2M1hAlO8nLhkNuKNxf66xHy.YlOj9vBkIZtAlZf WwZswZPWMOE.h5uNL23ap8eKH_S.oIwPFo7KVH1osIgOA8OofxHUt7QjZtG5 A47w5GW_Qc4LuSkTAUKN1EeOmpliq Received: from [83.100.146.195] by web26007.mail.ukl.yahoo.com via HTTP; Mon, 04 Apr 2011 17:23:40 BST X-Mailer: YahooMailClassic/12.0.2 YahooMailWebService/0.8.109.295617 Date: Mon, 4 Apr 2011 17:23:40 +0100 (BST) From: Glyn Astill Subject: Re: Bloated indexes from pg_restore? (Was: Index fillfactor changed in pg9?) To: Tom Lane Cc: Kenneth Marshall , pgsql-admin@postgresql.org In-Reply-To: <872.1301932933@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001 X-Spam-Level: X-Archive-Number: 201104/39 X-Sequence-Number: 37220 --- On Mon, 4/4/11, Tom Lane wrote:=0A> > So it appears= now that if I restore the database using=0A> pg_restore, I end up with blo= ated indexes, which are fixed=0A> with a vacuum full.=0A> =0A> > The dump i= s a data only dump with the -Fc flag,=0A> =0A> Data only dump?=A0 Then what= is the state of the=0A> database you're restoring=0A> it into?=0A> =0A=0AI= t's a newly created database from a schema only dump.