| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | nickf(at)ontko(dot)com |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk>, "pgsql-admin" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_restore error: function plpgsql_call_handler already exists with same argument types |
| Date: | 2002-12-02 15:22:50 |
| Message-ID: | 18517.1038842570@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Nick Fankhauser" <nickf(at)ontko(dot)com> writes:
> It appears that in the process of creating the schema, pg_restore attempted
> to create an object that required the existence of actor, which wasn't
> restored yet. My conjecture is that the objects are just being created in
> the wrong order.
Probably. You could check this by running pg_restore with query logging
turned on, to see what commands it's actually issuing -- or just do
"pg_restore -s" into a text file and eyeball the generated script.
There are a lot of situations where pg_dump fails to pick a safe reload
order at the moment (that's why pg_restore has that wild and woolly set
of options for manual adjustment of the reload order).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Elphick | 2002-12-02 16:41:01 | Re: pg_restore error: function plpgsql_call_handler |
| Previous Message | Nick Fankhauser | 2002-12-02 14:47:45 | Re: pg_restore error: function plpgsql_call_handler already exists with same argument types |