Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id A0EA19F9D9A; Mon, 10 Sep 2007 21:20:19 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 53386-01; Mon, 10 Sep 2007 21:20:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 834319F9CE8; Mon, 10 Sep 2007 21:20:16 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l8B0KCN4001368; Mon, 10 Sep 2007 20:20:13 -0400 (EDT) To: Alvaro Herrera cc: dx k9 , pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: reindexdb hangs In-reply-to: <20070910220700.GC3060@alvh.no-ip.org> References: <22018.1178144703@sss.pgh.pa.us> <20070825222150.GU31461@alvh.no-ip.org> <4909.1188082313@sss.pgh.pa.us> <20070829222341.GX7911@alvh.no-ip.org> <12577.1188428726@sss.pgh.pa.us> <20070830164151.GS5872@alvh.no-ip.org> <7460.1188500061@sss.pgh.pa.us> <20070910220700.GC3060@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Mon, 10 Sep 2007 18:07:00 -0400" Date: Mon, 10 Sep 2007 20:20:12 -0400 Message-ID: <1367.1189470012@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/56 X-Sequence-Number: 26817 Alvaro Herrera writes: > I am unsure if I should backpatch to 8.1: the code in cluster.c has > changed, and while it is relatively easy to modify the patch, this is a > rare bug and nobody has reported it in CLUSTER (not many people clusters > temp tables, it seems). Should I patch only REINDEX? How far back? I'd say go as far back as you can conveniently modify the patch for. This is a potential data-loss bug (even if only for temporary data) so we ought to take it seriously. regards, tom lane