From: | jwieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | Bill(dot)Allie(at)mug(dot)org |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Problem dumping PL/pgsql functions. |
Date: | 1998-10-05 07:17:57 |
Message-ID: | m0zQ4u6-000EBQC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> When I dumped (via pg_dump) a database that had PL/pgsql functions defined,
> the following happened:
>
> CREATE FUNCTION val0_id (int4 ) RETURNS text AS 'unknown' LANGUAGE 'unknown';
> CREATE FUNCTION val1_id (int4 ) RETURNS text AS 'unknown' LANGUAGE 'unknown';
> CREATE FUNCTION val0_sect (text,char ) RETURNS text AS 'unknown' LANGUAGE
> 'unknown';
> CREATE FUNCTION val1_sect (text,char ) RETURNS text AS 'unknown' LANGUAGE
> 'unknown';
>
> Apparently, pg_dump does not recognize/handle PL/pgsql functions yet.
Seems that pg_dump doesn't lookup pg_language but has the
languages hardcoded compiled in. That's not right. I'll take
a look at it.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1998-10-05 07:28:34 | Re: [HACKERS] plpgsql is not ready for prime time |
Previous Message | Billy G. Allie | 1998-10-05 05:55:30 | Re: [HACKERS] Make error in current cvs. |