Re: Storage Location Patch Proposal for V7.3

From: "Jim Buttafuoco" <jim(at)buttafuoco(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, jim(at)buttafuoco(dot)net, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Storage Location Patch Proposal for V7.3
Date: 2001-11-06 22:58:30
Message-ID: 200111062258.fA6MwUL07933@dual.buttafuoco.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)buttafuoco(dot)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
>
>

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-11-06 22:59:04 Re: Create or replace function doesn't work so well
Previous Message Peter Eisentraut 2001-11-06 22:53:55 Re: Proposal: 7.2b2 today