pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Richard J Kuhns <rjk@grauel.com>
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
Cc: Richard J Kuhns <rjk@grauel.com>
Cc: pgsql-general@postgresql.org
Subject: Re: Question about databases in alternate locations...
Date: Wed, 17 May 2000 08:50:27 -0500 (EST)
Message-ID: <14626.41891.173479.250021@localhost.grauel.com> (raw)
In-Reply-To: <39223072.63596770@alumni.caltech.edu>
References: <14625.26748.356187.68826@localhost.grauel.com>
	<39223072.63596770@alumni.caltech.edu>

Thomas Lockhart writes:
 > > 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

Thanks to everyone who answered; my problem was that the backend knew
nothing about it.

That brings up a comment, a question, and an offer.  First, the comment: I
actually did check the user's guide before I posted the question, but the
description of initlocation doesn't mention it at all -- it just gives an
example that doesn't work unless the backend already knows about the
variable.  It does refer to the CREATE DATABASE section, but at a quick
glance (I know, I should have read more carefully, mea culpa!) I just saw
an example that looked similar to the initlocation example.

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.

Now the offer.  I'm in the design stage of the process of converting a
fairly large legacy application to PostgreSQL.  It's going to be
essentially a complete re-write, but I should be able to do it in
more-or-less independent sections.  I really like what I've experienced so
far of PostgreSQL, I'd like to contribute, and modifying the postmaster to
use (or at least look at, if it exists) a system catalog for this info
might be a good way to get my feet wet.  Comments?

Thanks...
				- Rich

-- 
Richard Kuhns			rjk@grauel.com
PO Box 6249			Tel: (765)477-6000 \
100 Sawmill Road				    x319
Lafayette, IN  47903		     (800)489-4891 /



view thread (10+ messages)  latest in thread

Message-ID: <14626.41891.173479.250021@localhost.grauel.com>
Permalink:  ../14626.41891.173479.250021@localhost.grauel.com/
Also on:    postgresql.org/message-id/14626.41891.173479.250021@localhost.grauel.com

 · 

reply

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: rjk@grauel.com, lockhart@alumni.caltech.edu, 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>

* 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