It appears that I can select the rows, but not delete or update them.
# select ctid from files where ctid = '(53101,30)';
ctid
(53101,30)
(1 row)
# delete from files where ctid = '(53101,30)';
DELETE 0
# update files set fileid = 1000 where ctid = '(53101,30)';
UPDATE 0
#
-Ze
On Fri, 13 Aug 2004, Tom Lane wrote:
> It would be interesting to see the ctid, xmin, cmin, and xmax fields
> as well.
ctid |xmin|cmin|xmax| oid| fileid | userid
--++++--+-+-
(53101,
Zeki Mokhtarzada <[EMAIL PROTECTED]> writes:
> It appears that I can select the rows, but not delete or update them.
That's *very* odd, because it works for me. Is the same true of both
those duplicate rows, or did you only try the one with nonzero xmax?
I think there must be something we don'
Zeki Mokhtarzada <[EMAIL PROTECTED]> writes:
> The system is running on a Dell PowerEdge 2650 running RedHat 8. We had a
> kernel halt about two weeks ago that was caused by one of our disk mirrors
> failing. It could be that these problems were caused at that point in
> time and are just being n
Zeki Mokhtarzada <[EMAIL PROTECTED]> writes:
> Notice that 3787433 is duplicated. How could this have happened if that
> column is flagged as the primary key. Even more interesting:
> select oid, fileid, userid from files where userid = 1898598 order by
> fileid;
>oid| fileid | userid
I have a very strange bug with postgres 7.4.3. I have a table with about
15 million rows and recently, duplicate rows have started appearing.
For simplicity, let's say my table is as follows:
files
---
fileid integer -- Primary key generated by a sequence
userid integer -- id of use
