From: | Don Seiler <don(at)seiler(dot)us> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Using hba_file parameter and relative path |
Date: | 2017-09-28 18:47:20 |
Message-ID: | CAHJZqBBwn7dUO9nE6m7yPuOjXkyW2nbB--1BYpNTUKVs5HymWg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
In going through some parameter file cleanup and re-factoring, I've been
using the hba_file parameter to specify a non-standard file location. I
tried using a relative location, thinking it would be relative to $PGDATA
but in actuality it is relative to the pwd of my bash session that starts
the database.
For example, if I'm in /tmp when I run "pg_ctl start", it will look for the
hba_file value under /tmp. If I change to $PGDATA/pg_log, it will look
under there.
Obviously I can change to an absolute path and not worry about it, but I'm
curious if this is the intended behavior. Why would we want that hba_file
value to be relative to something as volatile as pwd?
FWIW this is Postgres 9.6.5 on CentOS 7.3.
Don.
--
Don Seiler
www.seiler.us
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-09-28 19:15:26 | Re: Using hba_file parameter and relative path |
Previous Message | Fabrízio de Royes Mello | 2017-09-27 17:42:44 | Re: dblink_tds or similar for PostgreSQL 10 |