This is just the first of many duplicate key errors that cause primary key
creation statements to fail on other tables. I grepped for the key but it
is hard to tell where the problem is with 888 matches.
I will try pg_dump --inserts. It is a 17G file with copy statements so...
this should be interesting. And take a long time.
On Fri, Dec 30, 2011 at 8:20 AM, Bèrto ëd Sèra <berto(dot)d(dot)sera(at)gmail(dot)com>wrote:
>> Are you sure there is just one record?
> What happens if you grep the backup file for "653009"?
> If you do have more than one such record, the quickest way out is to
> manually clean it.
> If Pac-Man had affected us as kids, we'd all be running around in a
> darkened room munching pills and listening to repetitive music.
In response to
pgsql-general by date
|Next:||From: Adrian Klaver||Date: 2011-12-30 16:57:21|
|Subject: Re: How to get the time zone offset|
|Previous:||From: Carlos Mennens||Date: 2011-12-30 16:50:57|
|Subject: Dated Version of PostgreSQL|