Re: BUG #1956: Plpgsql top-level DECLARE does not share - Mailing list pgsql-bugs

From Karl O. Pinc
Subject Re: BUG #1956: Plpgsql top-level DECLARE does not share
Date
Msg-id 1129303468l.20118l.6l@mofo
Whole thread Raw
In response to Re: BUG #1956: Plpgsql top-level DECLARE does not share  (Michael Fuhr <mike@fuhr.org>)
List pgsql-bugs
On 10/14/2005 09:30:51 AM, Michael Fuhr wrote:
>> On Thu, Oct 13, 2005 at 03:51:15PM +0000, Karl O. Pinc wrote:
> > I definately do not recall catching any additional errors at
> > compile time as part of the switch to 8.

>  8.0's syntax checking is minimal; 8.1's will be better.

Looking forward to it!

   Also, you
> might not even have plpgsql's lanvalidator function if you restored
> from an earlier version.  What's the result of the following query?
>
> SELECT * FROM pg_language WHERE lanname = 'plpgsql';
>
> If lanvalidator is 0 then you won't get even the minimal syntax
> checks.  8.1 will avoid this problem by creating languages based
> on entries in a template table (pg_pltemplate).

babase=# SELECT * FROM pg_language WHERE lanname = 'plpgsql';
  lanname | lanispl | lanpltrusted | lanplcallfoid | lanvalidator |
lanacl
---------+---------+--------------+---------------+--------------+--------
  plpgsql | t       | t            |         17239 |        17240 |
(1 row)

So I've got it.

IIRC I didn't have anything but test data at the time I upgraded
to 8.0 and so re-created all my databases.

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: A couple of ecpg issues in CVS tip
Next
From: C Wegrzyn
Date:
Subject: Re: BUG #1962: ECPG and VARCHAR