Re: pg_restore error: function plpgsql_call_handler already exists with same argument types

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-03 05:51:45
Message-ID: 20471.1038894705@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:
>> 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).

> Is this considered a bug, or a generally accepted limitation?

It's a bug, but one of long standing. It will not be fixed before 7.4
at the earliest (I *hope* someone is gonna tackle this for 7.4).

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Harry Yau 2002-12-03 09:13:09 Problem of Null Ordering
Previous Message Dan Langille 2002-12-02 23:23:02 Re: What kind of index to use for many rows with few unique