Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UhfQa-0001ma-7D for pgsql-performance@arkaria.postgresql.org; Wed, 29 May 2013 12:24:28 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UhfQZ-0001ac-L5 for pgsql-performance@arkaria.postgresql.org; Wed, 29 May 2013 12:24:27 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UhfQY-0001aW-F8 for pgsql-performance@postgresql.org; Wed, 29 May 2013 12:24:26 +0000 Received: from mail-wi0-x22d.google.com ([2a00:1450:400c:c05::22d]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UhfQR-00007B-Su for pgsql-performance@postgresql.org; Wed, 29 May 2013 12:24:25 +0000 Received: by mail-wi0-f173.google.com with SMTP id hi5so3475511wib.6 for ; Wed, 29 May 2013 05:24:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version:x-mailer:x-gm-message-state; bh=4lDOgObXF9rdJWbEF7j1F2UioQ+ZDvMFyUowRTU78l8=; b=K0snZ0lbvkvZLmAySFJ2C1Cwh885Yc9IrTVkxG8ZmlHmVfwtGEWjskcfPLJTdaoE7I aB4e/xWFyaSFuzhctr/nI3RVOgVwmlpvwT5nmBZFfS95oTv1pn2TNsvpwH7eeVYV+Jz9 z/6ziQ77FNTZTN1JkigJx4uuaYmNof0HOAYTKRqS2or+AB64f3iJDo/QJYEl+TeXZGNe 5ldFLM+nt7s0ztfzPkB67fGtOyFDPDoIhVK407vSxKoFk5mQtMjKlcvNjPvNpCyKpHgH m0IKKllJ8ZA/leX80U620s29hECUouSfi8iLerxYjuiBk02up5pXcAB/uZafyy32n2QQ ULKw== X-Received: by 10.180.187.234 with SMTP id fv10mr1643370wic.29.1369830257751; Wed, 29 May 2013 05:24:17 -0700 (PDT) Received: from [192.168.1.62] (0905ds8-ar.0.fullrate.dk. [90.185.25.212]) by mx.google.com with ESMTPSA id x13sm30884764wib.3.2013.05.29.05.24.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 May 2013 05:24:16 -0700 (PDT) From: =?iso-8859-1?Q?Niels_Kristian_Schj=F8dt?= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Best practice when reindexing in production Message-Id: <5359686B-FAE8-4056-AF13-F9FD6919FE82@autouncle.com> Date: Wed, 29 May 2013 14:24:14 +0200 To: "pgsql-performance@postgresql.org list" Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) X-Mailer: Apple Mail (2.1503) X-Gm-Message-State: ALoCoQlfA7rz+pc/x1CZ5wcxjpI+hYDmDmge8p6MA6K1bGLeb6lB2b6uUpidUlccjzZ0ifu+KiBx X-Pg-Spam-Score: 0.8 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Hi, I have a database with quite some data (millions of rows), that is heavily = updated all the time. Once a day I would like to reindex my database (and m= aybe re cluster it - don't know if that's worth it yet?). I need the databa= se to be usable while doing this (both read and write). I see that there is= no way to REINDEX CONCURRENTLY - So what approach would you suggest that I= take on this? Regards Niels Kristian --=20 Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance