Alternate data locations - Mailing list pgsql-general

From Rich Shepard
Subject Alternate data locations
Date
Msg-id Pine.LNX.4.30.0103271405330.27224-100000@salmo.appl-ecosys.com
Whole thread Raw
List pgsql-general
  Back in the old days of 6.x, the use of alternate database locations (for
example, by defining $PGDATA2 wherever I wanted it to be located) didn't
work. This was scheduled to be fixed in 7.x. Has it?

  I want to use postgres as the attribute-storing dbms for my GRASS (GIS)
projects. What I'd like to do is store attribute data in each project
directory, along with the spatial object files. I do want postgres to find
the proper data files, so I'll need to specify the proper path. But, the
question is whether or not postgres will now respond properly.

TIA,

Rich

Dr. Richard B. Shepard, President

                       Applied Ecosystem Services, Inc. (TM)
            2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
 + 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com


pgsql-general by date:

Previous
From: Alex Howansky
Date:
Subject: Re: Logging Queries
Next
From: Joel Dudley
Date:
Subject: fmgr, C , and character arguments