Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 9662764FD8C for ; Sat, 18 Oct 2008 04:00:23 -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 78507-09 for ; Sat, 18 Oct 2008 04:00:20 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by postgresql.org (Postfix) with ESMTP id C2EF264FCAC for ; Sat, 18 Oct 2008 04:00:20 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id b25so810988rvf.43 for ; Sat, 18 Oct 2008 00:00:19 -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:references; bh=vlPUNVMYrvFZnyvdgKLAruDnJt4jDpeZEUV9HS8FkSI=; b=U/5NhsO4WzG2eegYsVrW1jOt+Nb0ji4tJHaOnvMHMlLnoa4jNpyIPCRx8NUv2BEJ5b SNd+/0XO0EUpWCmI94fA6KhmFntsK/+v6iUlkBJ6r4zvOfpEwZ73yMuahNXTeLvPyyQs 7zWmf/hAiZRu3mCQqNudV4Z0bYt1VEXZZflxI= 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:references; b=e82SsZEzIeKOTBB2+oiu/yYfP/qimTLv2SdQC4gSVXLdNejUOXlXw+woYVG7TQcl7+ 7zL1AYNWC78fEY4cO6PnFOU7nDV5ZxZUPuXsKDaUDw4N+gqCXdyGRVOLdHGsrxeDvwFO 9gD2WgEd00fO7t/jApTiKmodiu9rNpJphvPAA= Received: by 10.140.226.14 with SMTP id y14mr3099423rvg.188.1224313219104; Sat, 18 Oct 2008 00:00:19 -0700 (PDT) Received: by 10.140.172.6 with HTTP; Sat, 18 Oct 2008 00:00:19 -0700 (PDT) Message-ID: <331e40660810180000x63b7116dkb2bfbebac4787c2@mail.gmail.com> Date: Sat, 18 Oct 2008 10:00:19 +0300 From: "=?ISO-8859-5?B?svbi0Nv22SDC2Nzn2OjY3Q==?=" To: "Tory M Blue" Subject: Re: Index bloat, reindex weekly, suggestions etc? Cc: pgsql-performance@postgresql.org In-Reply-To: <8a547c840810170905m7323dbd8x90de7dd004abc7d4@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_64477_17411548.1224313219085" References: <8a547c840810170905m7323dbd8x90de7dd004abc7d4@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200810/99 X-Sequence-Number: 31680 ------=_Part_64477_17411548.1224313219085 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 2008/10/17 Tory M Blue > > The real issue is my index growth and my requirement for weekly > re-indexing (which blocks and therefore is more or less a manual > process in a live production environment (fail over, changing vips > etc). > BTW: Can't you simply recreate indexes online? Since postgresql accepts multiple indexes of same definition, this may look like: 1) create index concurrently index_alt 2) analyze index_alt 3) drop index_orig Both index_alt and index_orig having same definition ------=_Part_64477_17411548.1224313219085 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline


2008/10/17 Tory M Blue <tmblue@gmail.com>

The real issue is my index growth and my requirement for weekly
re-indexing  (which blocks and therefore is more or less a manual
process in a live production environment (fail over, changing vips
etc).

BTW: Can't you simply recreate indexes online? Since postgresql accepts multiple indexes of same definition, this may look like:
1) create index concurrently index_alt
2) analyze index_alt
3) drop index_orig
Both index_alt and index_orig having same definition
------=_Part_64477_17411548.1224313219085--