Re: tables, where

On Thu, 29 Mar 2001, Richard Huxton wrote:

> From: "Martn Marqus" <martin(at)bugs(dot)unl(dot)edu(dot)ar>
>
> > Is it a bad idea to put tables of different aplications, even if they have
> > somethings in comun, in the same database?
>
> Plus points :

> Minus points :

As I have not received an answer to my posted question of a few days ago,
let me try again, under this thread. It's a related question.

The docs for the 6.x releases described how to use different data
directories under postgres. After trying unsuccessfully with a number of
different approaches, I asked the list and learned that this feature was
broken under 6.x but was scheduled to be working in the 7.x releases. My
question is whether or not (with 7.0.3 or 7.1) I can specify environment
variables such as $PGDATA2 and $PGDATA3, each pointing to a project-specific
data directory, and be able to have postgres recognize (and accept!) that
directory?

For example, (and this is what I tried with the 6.5.x series), in
~/.bash_profile I have this:

PGLIB=/usr/lib/pgsql
PGDATA=/var/lib/pgsql
PGDATA2=/home/rshepard/accounting/paisley
export PGLIB PGDATA PGDATA2

I went through the process of registering PGDATA2 with postgres
(supposedly), but I could not use this directory.

Could I now do this and have it work?

Thanks,

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