Re: [HACKERS] Re: [SQL] plpgsql error

From: jwieck(at)debis(dot)com (Jan Wieck)
To: tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane)
Cc: jwieck(at)debis(dot)com, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: [SQL] plpgsql error
Date: 1999-05-12 15:58:16
Message-ID: m10hbOi-000EBdC@orion.SAPserv.Hamburg.dsh.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> jwieck(at)debis(dot)com (Jan Wieck) writes:
> >> Perhaps this could be driven by a configuration switch?
>
> > Or maybe some switch to initdb and createdb?
>
> That's a good idea; it would save having to propagate the value out of
> configure and into the places where it'd be needed.

I've thought a little more about that one and I don't like it
anymore. It's a bad idea that enabling a language in such a
looser-friendly way is only possible during db creation, not
for existing databases.

I'll remove that from initdb again and instead add two new
utilities "installpl" and "removepl". That way it's also
possible to automate the process in scripts but it is as
flexible as can.

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) #

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ross J. Reedstrom 1999-05-12 16:08:05 BUG? serials and primary keys (was Re: [INTERFACES] Bug in psql?)
Previous Message Thomas Lockhart 1999-05-12 15:30:00 Re: [HACKERS] defalut value