From: | Wenzhe Zhou <wzhou(at)cisco(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pascal bérest <lists(at)magnetophone(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: duplicate key |
Date: | 2003-01-13 17:00:43 |
Message-ID: | 4.3.2.7.2.20030113085743.00ba3400@mira-sjc5-6.cisco.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I got same problem with Postgres 7.2.3. I kept a tar file for the whole data directory.
Wenzhe
At 11:24 AM 1/13/2003 -0500, Tom Lane wrote:
>pascal =?iso-8859-1?Q?b=E9rest?= <lists(at)magnetophone(dot)com> writes:
>>> Also, it would be useful to see the ctid, xmin, xmax, cmin,
>>> and cmax values for some of the sets of duplicate rows.
>
>> Could you explain where we can have these informations ?
>
>Select 'em. They're system columns, like OID.
>
>> We also delete the duplicate keys, but we still have some of them.
>> We delete again and again, and we still have some of them. Finally,
>> we delete them manually, and it was possible to REINDEX the table.
>
>So in other words, the evidence is now all gone? Oh well.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
From | Date | Subject | |
---|---|---|---|
Next Message | Lincoln Yeoh | 2003-01-13 18:21:29 | Re: forum - Software |
Previous Message | pascal bérest | 2003-01-13 16:51:28 | Re: duplicate key |