From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lukasz Brodziak <lukasz(dot)brodziak(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Schema with OID 0 does not exist in pg_dump |
Date: | 2011-09-05 16:46:01 |
Message-ID: | 8881.1315241161@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Lukasz Brodziak <lukasz(dot)brodziak(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Lukasz Brodziak | 2011-09-05 16:51:01 | Re: Schema with OID 0 does not exist in pg_dump |
Previous Message | Lukasz Brodziak | 2011-09-05 11:06:33 | Re: Schema with OID 0 does not exist in pg_dump |