Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 6B0CB1337B58 for ; Wed, 6 Oct 2010 17:31:24 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 11070-04 for ; Wed, 6 Oct 2010 20:31:17 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from nm27.bullet.mail.ne1.yahoo.com (nm27.bullet.mail.ne1.yahoo.com [98.138.90.90]) by mail.postgresql.org (Postfix) with SMTP id 5D6771337B56 for ; Wed, 6 Oct 2010 17:31:15 -0300 (ADT) Received: from [98.138.90.48] by nm27.bullet.mail.ne1.yahoo.com with NNFMP; 06 Oct 2010 20:31:15 -0000 Received: from [98.138.89.245] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 06 Oct 2010 20:31:15 -0000 Received: from [127.0.0.1] by omp1059.mail.ne1.yahoo.com with NNFMP; 06 Oct 2010 20:31:15 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 117431.5818.bm@omp1059.mail.ne1.yahoo.com Received: (qmail 85839 invoked by uid 60001); 6 Oct 2010 20:31:15 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1286397075; bh=QWNTNRMLFAV9atlL3GZ0WFKyE2Suf9U+0vlamENfC8w=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=htZtJuQqOO75om23D05b+OrYkQKNZr8Bzrtc48czaMnk+wbwnFSpQW3f1cTdDSXWyfksBxTrC5v4gLPMjdH+MEsJafvn4qm9NaBrxVxBhkwvAUJjWZ2EWN0HACCUiQ6GvAbm4E1ULiqsgAuMxQmj+moHfwa7v7i9ywuUt/jikNM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=iNhO1mOw+FvR8z/rH1sab9UBi57iIHuJTjY7O5g2PalB7rGDAhFSHhowxVmQxcbjxDxJ1KtfLJUBao6na9MQMstcM3ark1cfi+l5rpr929o+4XsPvaqGsDEacGJbAS95l948wM0oos+drtdlhtpivbGfw0FGH4T6fO4hqE23YoU=; Message-ID: <5674.85628.qm@web120004.mail.ne1.yahoo.com> X-YMail-OSG: DF4Xq1gVM1kt3MXWmf1uK6AohW4lX6HppMkxt.Fnkj.bg7_ u4v7RnGb7lzfJxeN619e6XTouIiZipWuGxwMUTLcoJceXZJG0IW4t9OY7vP7 DGE4lzsWOCcWmeHw6g.xYsPakEw3ZF8zhd__1vmh6J.qwnZhJARYGfB0s4s9 Z6kad1XjEDag.AMCIAmKTi6yQrL4Q9kKFbWjQzw-- Received: from [204.62.12.21] by web120004.mail.ne1.yahoo.com via HTTP; Wed, 06 Oct 2010 13:31:14 PDT X-Mailer: YahooMailRC/497 YahooMailWebService/0.8.106.282862 Date: Wed, 6 Oct 2010 13:31:14 -0700 (PDT) From: A J Subject: Restore rather than rebuild index ? To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-540560899-1286397074=:85628" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.138 tagged_above=-10 required=5 tests=BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: ** X-Archive-Number: 201010/65 X-Sequence-Number: 35806 --0-540560899-1286397074=:85628 Content-Type: text/plain; charset=us-ascii During restore of a database (from a full backup), the general practice is to rebuild the indexes. I think with pg_dump and pg_restore (or psql restore), the only option is to rebuild the indexes. Am I right or is it possible to backup indexes as well and restore them ? Just exploring, to figure if time to rebuild a fully functional database (with indexes) can be lower one way or the other. Thank you, AJ --0-540560899-1286397074=:85628 Content-Type: text/html; charset=us-ascii
During restore of a database (from a full backup), the general practice is to rebuild the indexes. I think with pg_dump and pg_restore (or psql restore), the only option is to rebuild the indexes. Am I right or is it possible to backup indexes as well and restore them ?
Just exploring, to figure if time to rebuild a fully functional database (with indexes) can be lower one way or the other.

Thank you,
AJ

--0-540560899-1286397074=:85628--