From: | Adrian Klaver <aklaver(at)comcast(dot)net> |
---|---|
To: | gastonq(at)allytech(dot)com |
Cc: | tango(at)allytech(dot)com, pgsql-general(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: pg_dump ERROR, usename "postgres" duplicated |
Date: | 2009-12-29 18:03:19 |
Message-ID: | 1872446039.6062401262109799596.JavaMail.root@sz0030a.emeryville.ca.mail.comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
----- "Gastón Quiroga" <gastonq(at)allytech(dot)com> wrote:
> Thank You Tom:
> I'll Try to make an update, but the 2 fields are equals row by row,
> how could I make a difference in the "WHERE" statement?
>
> Regards
>
> Gastón Quiroga
> Allytech S.A.
>
> Tom Lane wrote:
>
> =?ISO-8859-1?Q?Gast=F3n?= <tango(at)allytech(dot)com> writes:
>
> It's Postgres version 8.0.8 Well, that's pretty ancient, and I see at
> least one bug in the release
> history that could result in duplicated rows. I'd counsel an update
> to
> 8.0.something-recent. You can probably delete the extra row using
> a WHERE on ctid.
>
> regards, tom lane
Per Toms previous post use the following query:
select ctid,xmin,xmax,* from pg_shadow;
Then use the ctid value of the duplicate value in the where clause.
Adrian Klaver
aklaver(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fork | 2009-12-29 18:12:19 | Re: Planner Row Estimate with Function |
Previous Message | Alvaro Herrera | 2009-12-29 17:57:33 | Re: pg_dump ERROR, usename "postgres" duplicated |