Re: Storage Location Patch Proposal for V7.3 - Mailing list pgsql-hackers

From Jim Buttafuoco
Subject Re: Storage Location Patch Proposal for V7.3
Date
Msg-id 200111062258.fA6MwUL07933@dual.buttafuoco.net
Whole thread Raw
In response to Storage Location Patch Proposal for V7.3  ("Jim Buttafuoco" <jim@buttafuoco.net>)
List pgsql-hackers
Tom,

I was just looking for a way to keep different postmasters out of each
others way.  If you think the DBA can do it great or if the DBA changes
port have him/her fix the locations.

Jim

> "Jim Buttafuoco" <jim@buttafuoco.net> writes:
> >   As for the actual data file location, I believe under each loc oid
we
> > would have pg_port #/DB OID/pg_class OID might be the way to go.  
> 
> Introducing pg_port into the paths would be a bad idea, since it
> would prevent restarting a postmaster with a different port number.
> I think if a DBA is running multiple postmasters, it's up to him
> to avoid pointing more than one of them at the same "location"
> directory.  (Maybe we could enforce that with lock files?  Not
> sure it's worth the trouble though.)
> 
>             regards, tom lane
> 
> 




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Create or replace function doesn't work so well
Next
From: Brent Verner
Date:
Subject: Re: RelationFlushRelation() or RelationClearRelation()