Skip site navigation (1) Skip section navigation (2)

Re: SELECT returning too many rows (?)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: rob <rob(at)dsvr(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org,Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
Subject: Re: SELECT returning too many rows (?)
Date: 2005-02-08 16:12:30
Message-ID: 6965.1107879150@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
rob <rob(at)dsvr(dot)net> writes:
> processing=# select oid,  ctid, xmin, cmin, xmax, cmax from q_certs
> where oid = 15282219 ;
>    oid    | ctid  |   xmin    |   cmin    |   xmax    |   cmax   
> ----------+-------+-----------+-----------+-----------+-----------
>  15282219 | (3,5) | 174011432 |         1 |         1 | 174214469
>  15282219 | (5,5) | 174011432 |         1 |         1 | 174214469
>  15282219 | (7,5) | 174011432 | 174700216 | 174700216 |         1

This looks to me like malfeasance of a VACUUM FULL: the reason there
are multiple copies is that VACUUM FULL was trying to move the row
around, and somehow you ended up with all three copies marked "good",
when there should have been only one "good" copy at any instant.

So: (1) have you had any system crashes recently?  (2) what sort of
disk hardware is this running on?  I'm wondering about IDE drives
with write caching enabled :-(

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2005-02-08 16:14:00
Subject: Re: SELECT returning too many rows (?) [7.4.2]
Previous:From: Tom LaneDate: 2005-02-08 15:57:48
Subject: Re: bug: erroronous ret-value for system() call in 2.6-kernel

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group