From: wieck@debis.com
To: tgl@sss.pgh.pa.us
Cc: patrickdlogan@home.com
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-docs@postgreSQL.org
Subject: Re: [HACKERS] Re: Problem enabling pltcl
Date: Thu, 9 Sep 1999 12:58:56 +0200 (MET DST)
Message-ID: <m11P1uq-0003kLC@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <1240.936826965@sss.pgh.pa.us>
Tom Lane wrote:
> But if the install process were to install pltcl into template1 just
> because you had chosen to build pltcl, then you'd lose the option of
> only having it in some of your databases.
You still have that option even if it is installed in
template1. But you must do it the other way round and use
destroydb on the databases where you don't want it :-)
> Bottom line: I think the install process is correct as is, but the docs
> need to be updated to mention these considerations.
The docs where right for a short time during v6.5
development.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck@debis.com (Jan Wieck) #
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: wieck@debis.com, tgl@sss.pgh.pa.us, patrickdlogan@home.com, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] Re: Problem enabling pltcl
In-Reply-To: <m11P1uq-0003kLC@orion.SAPserv.Hamburg.dsh.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox