pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: dx k9 <bitsandbytes88@hotmail.com>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: reindexdb hangs
Date: Mon, 10 Sep 2007 20:20:12 -0400
Message-ID: <1367.1189470012@sss.pgh.pa.us> (raw)
In-Reply-To: <20070910220700.GC3060@alvh.no-ip.org>
References: <BAY116-F2261C1BEF758D30196729DD1420@phx.gbl>
	<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>

Alvaro Herrera <alvherre@commandprompt.com> 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



view thread (14+ messages)  latest in thread

Message-ID: <1367.1189470012@sss.pgh.pa.us>
Permalink:  ../1367.1189470012@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1367.1189470012@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, alvherre@commandprompt.com, bitsandbytes88@hotmail.com, pgsql-hackers@postgresql.org
  Subject: Re: reindexdb hangs
  In-Reply-To: <1367.1189470012@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox