From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard J Kuhns <rjk@grauel.com>
Cc: Thomas Lockhart <lockhart@alumni.caltech.edu>
Cc: pgsql-general@postgresql.org
Subject: Re: Question about databases in alternate locations...
Date: Wed, 17 May 2000 12:35:14 -0400
Message-ID: <17483.958581314@sss.pgh.pa.us> (raw)
In-Reply-To: <14626.41891.173479.250021@localhost.grauel.com>
References: <14625.26748.356187.68826@localhost.grauel.com>
<39223072.63596770@alumni.caltech.edu>
<14626.41891.173479.250021@localhost.grauel.com>
Richard J Kuhns <rjk@grauel.com> writes:
> Now for the question. What's the reason for using this method, as opposed
> to using, say, a system catalog to hold the valid locations? Historical?
> Having to stop and restart the backend so it can re-read its environment
> seems kind of archaic.
Well, there'd be a certain amount of circularity in consulting a table
to find out where you can find tables, no? ;-) But you're right, the
environment-variable mechanism is pretty grotty. There's been a great
deal of discussion already in pg-hackers about how to clean up this
and related issues; suggest you consult the archives if you want to get
involved with fixing it.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, rjk@grauel.com, lockhart@alumni.caltech.edu, pgsql-general@postgresql.org
Subject: Re: Question about databases in alternate locations...
In-Reply-To: <17483.958581314@sss.pgh.pa.us>
References: <14625.26748.356187.68826@localhost.grauel.com> <39223072.63596770@alumni.caltech.edu> <14626.41891.173479.250021@localhost.grauel.com> <17483.958581314@sss.pgh.pa.us>
* 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