Re: [SQL] pg primary key bug?

[pginfo]

Hi,

Tom Lane wrote:

pginfo <[EMAIL PROTECTED]> writes:
  

Tom Lane wrote:
    

Could we see the system columns on these rows?
      

01=# select oid,xmin,cmin,xmax,cmax,ctid,* from a_constants_str where 
constname='DOCPLAID';
  oid  |  xmin   |  cmin   |  xmax   | cmax |  ctid  | constname | fid | 
constvalue
-------+---------+---------+---------+------+--------+-----------+-----+------------
 17916 | 2232893 | 2235861 | 2235861 |   42 | (4,71) | DOCPLAID  |   0 | 
SOF_19738
 17916 | 2232893 | 2235861 | 2235861 |   41 | (7,62) | DOCPLAID  |   0 | 
SOF_19738
(2 rows)
    

Given the identical OID and xmin values, it seems certain that these are
the "same" row, ie there was only one insertion event.  My bet is that
the one at (7,62) is the original, and that the one at (4,71) is a copy
that was made by VACUUM FULL trying to move the row to compact the
table.  So the question is how did both copies get to be marked
simultaneously valid?  That should be impossible, unless a disk write
got dropped.  Have you had any system crashes during VACUUM FULL
operations recently?

			regards, tom lane


  

I do not know exact, but it is possible.
This is customer server and I do not have any info about server/os crash, but I am 100% sure.
I will ask as soon as possible and replay.
Also I will check the logs.
We start pg witl pg_ctl ...-D... -l  /logfile  and if we can found the needet info in pg log file I can check it ( I do not nkow what to search in this file).
We are running vacuum once per 24 h.
The OS is RedHat AS 3.
PostgreSQL is 7.4.1 (but we have the same problem on 7.4.5).

Will upgrade to 8.0 solve this type of problems ?

regards,
ivan.