Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 8B24A9FB1DE for ; Mon, 25 Sep 2006 19:38:19 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 68526-04 for ; Mon, 25 Sep 2006 19:38:17 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.224]) by postgresql.org (Postfix) with ESMTP id AB5159FA318 for ; Mon, 25 Sep 2006 19:38:16 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id t13so2065780wxc for ; Mon, 25 Sep 2006 15:38:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=iGcwl75h8vW+Rkfry0FEEwa+WTX13vmSeJy1xJJtRyqrjcJ1cSFWlIhT+NC4K9hcjp4x/YYEwDs4XvfCn93tALB3ZaJGk51f0VVy2dXxfmU8fkujwkVlIio2WUXvONEIIaaDpuyHw7Qlk8YfeaQPCN1H4OLU6cO3GYxpw1VxPdw= Received: by 10.90.55.19 with SMTP id d19mr7566aga; Mon, 25 Sep 2006 15:38:10 -0700 (PDT) Received: by 10.90.93.9 with HTTP; Mon, 25 Sep 2006 15:38:10 -0700 (PDT) Message-ID: <1c66bda80609251538g73899f2m8edd01290d1214f6@mail.gmail.com> Date: Tue, 26 Sep 2006 10:38:10 +1200 From: adey To: "Tom Lane" Subject: Re: WAL configuration and REINDEX Cc: pgsql-admin@postgresql.org In-Reply-To: <1c66bda80609242019k4969aa97taf56e2ae30d3bf29@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_36373_10459928.1159223890374" References: <45126C37.6020106@gva.es> <8CC6FC7A-C737-4473-99E1-9860FA61D9C5@enterprisedb.com> <1c66bda80609241523p2c111042p96bb2f935da08f51@mail.gmail.com> <13160.1159140743@sss.pgh.pa.us> <1c66bda80609242019k4969aa97taf56e2ae30d3bf29@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.383 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/278 X-Sequence-Number: 23192 ------=_Part_36373_10459928.1159223890374 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Tom, Further to my request below, the following recommendation exists in the Postgres 8.1 documentation:- http://www.postgresql.org/docs/8.1/interactive/routine-reindex.html On 9/25/06, adey wrote: > > Thanks Tom. > How does Postgres handle page splits and redirections in indexes then > please? > I had an unsuccessful look at :- > http://www.postgresql.org/docs/8.1/interactive/index-functions.html > > and > > http://www.postgresql.org/docs/8.1/interactive/indexes-types.html > > > On 9/25/06, Tom Lane wrote: > > > > adey writes: > > > I apologise if I am uninformed, but it is my understanding that > > REINDEX is > > > still required even with the most regular of vacuums? > > > > REINDEX shouldn't be required at all under normal circumstances. > > > > regards, tom lane > > > > ------=_Part_36373_10459928.1159223890374 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hi Tom,
Further to my request below, the following recommendation exists in the Postgres 8.1 documentation:-


 
On 9/25/06, adey <adey11@gmail.com> wrote:
Thanks Tom.
How does Postgres handle page splits and redirections in indexes then please?
I had an unsuccessful look at :-
 
and
 
On 9/25/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
adey < adey11@gmail.com> writes:
> I apologise if I am uninformed, but it is my understanding that REINDEX is
> still required even with the most regular of vacuums?

REINDEX shouldn't be required at all under normal circumstances.

                       regards, tom lane


------=_Part_36373_10459928.1159223890374--