From: | Lukasz Brodziak <lukasz(dot)brodziak(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Schema with OID 0 does not exist in pg_dump |
Date: | 2011-09-05 16:51:01 |
Message-ID: | CAGWYGjXRJj=zuGEJV0ckVn4Zf9Hb92Q+7e3aQFCVbGBMb9Z+ZQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
Just managed to complete the pg_dump by replacing the broken pg_operator
file with the one from non-broken database then I read what You've written.
Now I can go further with the DB :-) Thanks a lot for the guidelines Tom.
Regards
Luke
2011/9/5 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> 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
>
--
Łukasz Brodziak
"Do you bury me when I'm gone
Do you teach me while I'm here
Just as soon I belong
Then it's time I disappear"
From | Date | Subject | |
---|---|---|---|
Next Message | marvin.deoliveira | 2011-09-05 18:07:42 | Can't create a new database from dump |
Previous Message | Tom Lane | 2011-09-05 16:46:01 | Re: Schema with OID 0 does not exist in pg_dump |