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 KAA99053; Tue, 11 Jan 2000 10:14:22 -0500 (EST) (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 KAA04282; Tue, 11 Jan 2000 10:14:10 -0500 (EST) To: Peter Eisentraut cc: pgsql-sql@postgreSQL.org, pgsql-hackers@postgreSQL.org Subject: Re: [SQL] createdb -D xxxx not working In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Tue, 11 Jan 2000 14:26:42 +0100" Date: Tue, 11 Jan 2000 10:14:10 -0500 Message-ID: <4279.947603650@sss.pgh.pa.us> From: Tom Lane [hackers added to cc: list] Peter Eisentraut writes: > On 2000-01-08, Tom Lane mentioned: >> Chris Griffin writes: >>>> # setenv PGDATA2 /web/sites/1.192/db-data >>>> # initlocation PGDATA2 >>>> # createdb -D PGDATA2 >> >> Surely you want $PGDATA2 in the latter two lines? > You might recall me mentioning that the whole alternative location > business doesn't work in the first place. I'll fix that this week; Chris > will have to wait until the next release. Fine. BTW, am I the only one who thinks that it's really silly for initlocation to expect to be given an unexpanded environment variable name? That's not normal practice (either elsewhere in Postgres, or anywhere else that I know of). It's confusing because it's not how an ordinary Unix user would expect a shell command to behave, and it doesn't buy any functionality that I can see. I'd vote for taking out the auto-expansion, so that the correct invocation becomes initlocation $PGDATA2 which is what an average user would expect. Actually, after looking at what initlocation really does, which is darn near nothing, I wonder whether we shouldn't dispense with it altogether... regards, tom lane