Re: BUG #8577: pg_dump custom format exported dump can't be imported again

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Dominik Dorn <dominik(at)dominikdorn(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #8577: pg_dump custom format exported dump can't be imported again
Date: 2013-11-05 21:59:24
Message-ID: 1383688764.54878.YahooMailNeo@web162902.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Dominik Dorn <dominik(at)dominikdorn(dot)com> wrote:

> How do I delete it from there there?
> lyriks=> DELETE FROM lytartist where ctid = (284,60);
> ERROR:  operator does not exist: tid = record
> LINE 1: DELETE FROM lytartist where ctid = (284,60);
>                                         ^
> HINT:  No operator matches the given name and argument type(s).
> You might need to add explicit type casts.

DELETE FROM lytartist where ctid = '(284,60)';

> And how can I prevent inserts like these in the future?

I would start by applying any updates available for the firmware,
OS, storage drivers, and PostgreSQL.  And I would probably schedule
a hardware check for the next suitable maintenance window.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-11-05 23:24:33 Re: Bad pg_stats.correlation with repeated keys.
Previous Message John R Pierce 2013-11-05 21:51:20 Re: BUG #8577: pg_dump custom format exported dump can't be imported again