From: | "Mark Mikulec" <mm98au(at)brocku(dot)ca> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Help! Can't pg_dump anything: handler procedure for procedural language plpgsql not found |
Date: | 2003-08-13 05:36:30 |
Message-ID: | 000c01c3615c$d972a2c0$6401a8c0@eros |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Unfortunately,
That didn't work.
Thanks anyway.
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mark Mikulec" <mm98au(at)badger(dot)ac(dot)brocku(dot)ca>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: Tuesday, August 12, 2003 9:54 AM
Subject: Re: [GENERAL] Help! Can't pg_dump anything: handler procedure for
procedural language plpgsql not found
> mm98au(at)brocku(dot)ca (Mark Mikulec) writes:
> > But i'd always get the following error message:
> > pg_dump: handler procedure for procedural language plpgsql not found
>
> Do you have any functions written in plpgsql? (I'm guessing not, or you
> would have other problems besides pg_dump not working.) If not, you can
> just delete the pg_language entry for plpgsql:
>
> DELETE FROM pg_language WHERE lanname = 'plpgsql';
>
> If you do have any such functions, you should drop them first.
> (Alternatively, let pg_dump find them for you, and drop them in response
> to its complaints.)
>
> regards, tom lane
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Mikulec | 2003-08-13 05:44:20 | Re: Help! Can't pg_dump anything: handler procedure for procedural language plpgsql not found |
Previous Message | Joshua D. Drake | 2003-08-13 05:09:27 | Re: PostGreSQL - Accessing It |