From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Dave Page" <dpage(at)postgresql(dot)org> |
Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, "Mark Cave-Ayland" <mark(dot)cave-ayland(at)ilande(dot)co(dot)uk> |
Subject: | Re: Locating sharedir in PostgreSQL on Windows |
Date: | 2007-11-26 22:30:17 |
Message-ID: | 4663.1196116217@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Dave Page" <dpage(at)postgresql(dot)org> writes:
> Yes, I know. Peter seemed to be saying that nothing except postgres
> itself should be in *any* of the installation directories
Yeah, that's what I think he said too, but it strikes me as a completely
bogus policy --- what about contrib modules or stuff from pgfoundry
or any random user-written module that was built with PGXS? All that
stuff happily drops files under $libdir and $sharedir, and I see no good
argument why it shouldn't.
There is fair room for argument about whether $sharedir is the
appropriate place for installation-specific config files though.
Those should probably live in the same place as postgresql.conf
and friends, ie, typically but not necessarily $PGDATA. It doesn't
look like SelectConfigFiles() saves the config directory name anyplace
where an add-on module could get at it. We could perhaps fix that for
8.3, but it won't help Mark if he insists on a backwards-compatible
solution. I suppose he could copy ConfigFileName and strip the last
component from it?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2007-11-26 22:31:06 | Re: [GENERAL] Empty arrays with ARRAY[] |
Previous Message | Dave Page | 2007-11-26 22:19:24 | Re: Locating sharedir in PostgreSQL on Windows |