pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: arnaulist@andromeiberica.com
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Very strange postgresql behaviour
Date: Mon, 29 Jan 2007 10:35:53 -0500
Message-ID: <10668.1170084953@sss.pgh.pa.us> (raw)
In-Reply-To: <45BDE670.8010607@andromeiberica.com>
References: <45BDE670.8010607@andromeiberica.com>

Arnau <arnaulist@andromeiberica.com> writes:
>    I have postgresql 7.4.2 running on debian and I have the oddest 
> postgresql behaviour I've ever seen.

Is this specific to these two rows?  If so it might be a case of this
bug, which was repaired in 7.4.13:

http://archives.postgresql.org/pgsql-general/2006-05/msg00756.php
http://archives.postgresql.org/pgsql-committers/2006-05/msg00174.php

2006-05-19 12:31  tgl

	* src/backend/executor/nodeIndexscan.c (REL7_4_STABLE): Fix nasty
	bug in nodeIndexscan.c's detection of duplicate tuples during a
	multiple (OR'ed) indexscan.  It was checking for duplicate
	tuple->t_data->t_ctid, when what it should be checking is
	tuple->t_self.	The trouble situation occurs when a live tuple has
	t_ctid not pointing to itself, which can happen if an attempted
	UPDATE was rolled back.  After a VACUUM, an unrelated tuple could
	be installed where the failed update tuple was, leading to one live
	tuple's t_ctid pointing to an unrelated tuple.	If one of these
	tuples is fetched by an earlier OR'ed indexscan and the other by a
	later indexscan, nodeIndexscan.c would incorrectly ignore the
	second tuple.  The bug exists in all 7.4.* and 8.0.* versions, but
	not in earlier or later branches because this code was only used in
	those releases.  Per trouble report from Rafael Martinez Guerrero.

REINDEX wouldn't fix this, although a table dump and reload would.

			regards, tom lane

PS: please don't spam multiple lists with the same question.



view thread (7+ messages)  latest in thread

Message-ID: <10668.1170084953@sss.pgh.pa.us>
Permalink:  ../10668.1170084953@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/10668.1170084953@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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, arnaulist@andromeiberica.com
  Subject: Re: Very strange postgresql behaviour
  In-Reply-To: <10668.1170084953@sss.pgh.pa.us>
  References: <45BDE670.8010607@andromeiberica.com> <10668.1170084953@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