From: | "Rob Long" <rlong(at)micropat(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_restore fails - postgres 7.3.4 |
Date: | 2003-10-03 13:20:28 |
Message-ID: | 846f5914.5914846f@micropat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom,
Will this be fixed in 7.4?
Thanks for the support.
Rob
----- Original Message -----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: Thursday, October 2, 2003 6:28 pm
Subject: Re: [ADMIN] pg_restore fails - postgres 7.3.4
> "Rob Long" <rlong(at)micropat(dot)com> writes:
> >>> Trying to dump and restore a production database with no success.
> >>>
> >>> pg_restore: [archiver (db)] could not execute query: ERROR:
> data type
> >>> integer has no default operator class for access method "gist"
> >>
> >> Hm, this is probably a matter of incorrect object restoration
> order ...
> >> could we see the output of "pg_restore -l" for this dump file?
>
> After playing around with this I realize that it's a bug
> associated with
> schemas --- if you have an operator class that's not in
> pg_catalog, the
> opclass name has to be explicitly qualified in pg_dump's output,
> or it
> won't restore correctly. I'm surprised no one reported this before,
> since it affects all the contrib operator classes.
>
> Attached is a patch against 7.3.4, in case it helps.
>
> regards, tom lane
>
>
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/plain | 1.6 KB |
unknown_filename | text/plain | 112 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-10-03 13:27:10 | Re: pg_restore fails - postgres 7.3.4 |
Previous Message | cad0022 | 2003-10-03 11:09:31 | How to avoid users from viewing functions code |