From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lukasz Brodziak <lukasz.brodziak@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Schema with OID 0 does not exist in pg_dump
Date: Mon, 05 Sep 2011 12:46:01 -0400
Message-ID: <8881.1315241161@sss.pgh.pa.us> (raw)
In-Reply-To: <CAGWYGjVRmc_=TqnE-p9e1sHXOZK3F15Wtk-+=J5wa4632er_6A@mail.gmail.com>
References: <CAGWYGjWxx8JO+jmynXh1vFsSRh1s62qPnSqzoY4L1dTyY+KCOw@mail.gmail.com>
<25644.1314885154@sss.pgh.pa.us>
<CAGWYGjVRmc_=TqnE-p9e1sHXOZK3F15Wtk-+=J5wa4632er_6A@mail.gmail.com>
Lukasz Brodziak <lukasz.brodziak@gmail.com> writes:
> Ok, I've found the rows theyh were placed in pg_operator table. After
> deletion I get the following error in pg_dump:
> pg_dump: Error message from server: ERROR: operator is not unique: smallint
> <> integer
> LINE 1: ...d = relowner) AS rolname, relchecks, (reltriggers <> 0) AS r...
> ^
> HINT: Could not choose a best candidate operator. You may need to add
> explicit type casts.
Kinda looks like you deleted some rows you shouldn't have ... the above
is about what I'd expect to happen if you'd removed the int2 <> int4
operator. Do you know what you removed, exactly? You might try
comparing the contents of pg_operator with another, non-broken database,
and putting back whatever's missing.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, lukasz.brodziak@gmail.com
Subject: Re: Schema with OID 0 does not exist in pg_dump
In-Reply-To: <8881.1315241161@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox