Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA75573 for ; Wed, 17 May 2000 01:34:37 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id FAA25669; Wed, 17 May 2000 05:38:58 GMT Message-ID: <39223072.63596770@alumni.caltech.edu> Date: Wed, 17 May 2000 05:38:58 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: Richard J Kuhns CC: pgsql-general@postgresql.org Subject: Re: Question about databases in alternate locations... References: <14625.26748.356187.68826@localhost.grauel.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200005/58 > Could anyone please tell me what I'm doing wrong? I'm sure I'm just > overlooking something, but what? As Jeff pointed out, the environment variable "P" must be known to the server backend to be used in the WITH LOCATION clause. Using it in the preceeding initlocation invocation was correct. The utility tries it as an environment variable, then as an absolute path, so "initlocation P" and "initlocation $P" are both valid. You can make the environment variable known to the backend by defining it in the postgres account's .cshrc or .bashrc file, or by explicitly setting it before firing up the backend. - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California