On 04/06/2017 08:01 PM, rob stone wrote:
On Thu, 2017-04-06 at 15:58 -0700, Adrian Klaver wrote:
On 04/06/2017 03:16 PM, rob stone wrote:
Which is what has me confused. If you are using the postgresql-
common
system then the *.conf files should be in
/etc/postgresql/version/cluster_name/.
Where exactly is PGDATA and why is the *.conf file there?
It's always been in the PGDATA path and it has always worked.
The doco implies that PGDATA is the place for the *.conf files unless
overridden by the config_file parameter.
That is the default location and is generally the case in a source
install. Package maintainers can and do often put them elsewhere. AFAIK
the Debian/Ubuntu way using postgresql-common is to put them in
/etc/postgresql/version/cluster_name/. So on one of my Ubuntu 16.04
installs with Postgres 9.6.2:
aklaver@arkansas:~$ l /etc/postgresql/9.6/main/
total 56
drwxr-xr-x 2 postgres postgres 4096 Feb 11 16:23 ./
drwxr-xr-x 3 postgres postgres 4096 Feb 11 07:15 ../
-rw-r--r-- 1 postgres postgres 315 Feb 11 07:15 environment
-rw-r--r-- 1 postgres postgres 143 Feb 11 07:15 pg_ctl.conf
-rw-r----- 1 postgres postgres 4642 Feb 11 16:23 pg_hba.conf
-rw-r----- 1 postgres postgres 1636 Feb 11 07:15 pg_ident.conf
-rw-r--r-- 1 postgres postgres 22438 Feb 11 16:11 postgresql.conf
-rw-r--r-- 1 postgres postgres 317 Feb 11 07:15 start.conf
and PGDATA:
aklaver@arkansas:~$ sudo ls -al /var/lib/postgresql/9.6/main/
total 92
drwx------ 19 postgres postgres 4096 Apr 6 15:54 .
drwxr-xr-x 3 postgres postgres 4096 Feb 11 07:15 ..
drwx------ 6 postgres postgres 4096 Feb 11 16:06 base
drwx------ 2 postgres postgres 4096 Mar 22 12:22 global
drwx------ 2 postgres postgres 4096 Feb 11 07:15 pg_clog
drwx------ 2 postgres postgres 4096 Feb 11 07:15 pg_commit_ts
drwx------ 2 postgres postgres 4096 Feb 11 07:15 pg_dynshmem
drwx------ 4 postgres postgres 4096 Feb 11 07:15 pg_logical
drwx------ 4 postgres postgres 4096 Feb 11 07:15 pg_multixact
drwx------ 2 postgres postgres 4096 Mar 22 12:21 pg_notify
drwx------ 2 postgres postgres 4096 Feb 11 07:15 pg_replslot
drwx------ 2 postgres postgres 4096 Feb 11 07:15 pg_serial
drwx------ 2 postgres postgres 4096 Feb 11 07:15 pg_snapshots
drwx------ 2 postgres postgres 4096 Mar 22 12:21 pg_stat
drwx------ 2 postgres postgres 4096 Feb 11 07:15 pg_stat_tmp
drwx------ 2 postgres postgres 4096 Feb 11 07:15 pg_subtrans
drwx------ 2 postgres postgres 4096 Feb 11 07:15 pg_tblspc
drwx------ 2 postgres postgres 4096 Feb 11 07:15 pg_twophase
-rw------- 1 postgres postgres 4 Feb 11 07:15 PG_VERSION
drwx------ 3 postgres postgres 4096 Feb 11 07:15 pg_xlog
-rw------- 1 postgres postgres 88 Feb 11 07:15 postgresql.auto.conf
-rw------- 1 postgres postgres 133 Mar 22 12:21 postmaster.opts
-rw------- 1 postgres postgres 100 Mar 22 12:21 postmaster.pid
This is why I am trying to figure out if you are using the Debian packaging:
A) What is your PGDATA?
B) How postgresql.conf got there?
The reason it is important is that the next update will probably land
you back in the same situation that started this thread, unless we
figure out what is going on.
Another question:
Have you ever installed Postgres on this machine using something other
then the Debian packages?
Cheers,
Rob
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
