Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA89320 for ; Wed, 17 May 2000 12:35:45 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id MAA17486; Wed, 17 May 2000 12:35:14 -0400 (EDT) To: Richard J Kuhns cc: Thomas Lockhart , pgsql-general@postgresql.org Subject: Re: Question about databases in alternate locations... 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> Comments: In-reply-to Richard J Kuhns message dated "Wed, 17 May 2000 08:50:27 -0500" Date: Wed, 17 May 2000 12:35:14 -0400 Message-ID: <17483.958581314@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200005/75 Richard J Kuhns 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