Re: Configurable path to look up dynamic libraries - Mailing list pgsql-hackers

From teg@redhat.com (Trond Eivind Glomsrød)
Subject Re: Configurable path to look up dynamic libraries
Date
Msg-id xuyy9ryo1ea.fsf@halden.devel.redhat.com
Whole thread Raw
In response to Re: Configurable path to look up dynamic libraries  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Configurable path to look up dynamic libraries  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:

> teg@redhat.com (Trond Eivind Glomsrød) writes:
> > Tom Lane <tgl@sss.pgh.pa.us> writes:
> >> teg@redhat.com (Trond Eivind Glomsrød) writes:
> > You could search in a path... first sysconfdir, then datadir. 
> >> 
> >> Surely the other way around.
> 
> > Which could work as well - or just a switch to postmaster to tell it
> > which file to use.
> 
> I could live with a datadir-then-sysconfdir path search.  (It should be
> datadir first, since the sysconfdir file would serve as a system-wide
> default for multiple postmasters.)  Given that approach I see no real
> need for a postmaster switch.
> 
> Possibly the same approach should apply to all the config files we
> currently store in datadir?
> 
> There is a security issue here: stuff stored in datadir is not visible
> to random other users on the machine (since datadir is mode 700), but
> I would not expect sysconfdir to be mode 700.  

It could be (the RPMs specify a sysconfdir of /etc/pgsql)

> We'd need to think about the implications of allowing Postgres
> config files to be world-visible. 

The files doesn't need to be visible to others...

-- 
Trond Eivind Glomsrød
Red Hat, Inc.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Configurable path to look up dynamic libraries
Next
From: teg@redhat.com (Trond Eivind Glomsrød)
Date:
Subject: Re: Configurable path to look up dynamic libraries