Le 21 juil. 2014 17:34, "Scott Furry" <scott.wl.fu...@gmail.com> a écrit : > > > On 21/07/14 08:58 AM, Christoph Berg wrote: >> >> That split conf-data setup is supported by PostgreSQL, so it's not >> Debian to blame. I think it is a bug (or missing feature) that >> pg_read_file doesn't let you read files in the conf directory. >> >> What probably works is if you create a symlink in the data directory >> to /etc/postgresql for pg_hba.conf and postgresql.conf. >> > Its great that PostgreSQL supports split configuration/data directory. > > In one of the message threads I found, a dev from PostgreSQL mentioned that the functions in the adminpack were written to prevent using paths out of the log/data directory expressly for security reasons. And I understand that rationale. It makes sense. > > I couldn't fathom how pgAdmin built in a means to alter configuration files when it didn't work in one instance. I think it makes it difficult for pgAdmin devs to maintain consistency across platforms when one linux distribution does something "a little different" that isn't done elsewhere AFAIK. > > Maybe as part of the Debian packaging those symlinks should be created/installed as part of the server package? > But that's for the Debian dev's to sort out and discuss on the Debian forums. >
Well, truly honestly, I've never used and will never use the config editor from PgAdmin. It's not good enough to be useful and practical. I'd trust more a complete rewrite with the 9.4 ALTER SYSTEM statement. Of course, this is just my point of view.
