| From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Alternate data locations |
| Date: | 2001-03-27 22:09:08 |
| Message-ID: | Pine.LNX.4.30.0103271405330.27224-100000@salmo.appl-ecosys.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)appl-ecosys(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Dudley | 2001-03-27 22:45:17 | fmgr, C , and character arguments |
| Previous Message | markus jais | 2001-03-27 21:42:39 | how to load a sql-file???? |