| From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
|---|---|
| To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: initdb when data/ folder has mount points |
| Date: | 2018-02-21 23:17:12 |
| Message-ID: | alpine.LNX.2.20.1802211514430.29124@salmo.appl-ecosys.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 21 Feb 2018, Ron Johnson wrote:
> Apparently, initdb assumes that data/ is one big mount point. However, we
> have four mount points:
> /var/lib/pgsql/9.6/data/backup
> /var/lib/pgsql/9.6/data/base
> /var/lib/pgsql/9.6/data/pg_log
> /var/lib/pgsql/9.6/data/pg_xlog
Ron,
What command do you use? Here, on Slackware-14.2, /var/lib/psql/10.2/data/
contains:
PG_VERSION pg_ident.conf pg_snapshots pg_wal
base pg_logical pg_stat pg_xact
global pg_multixact pg_stat_tmp postgresql.auto.conf
pg_commit_ts pg_notify pg_subtrans postgresql.conf
pg_dynshmem pg_replslot pg_tblspc postmaster.opts
pg_hba.conf pg_serial pg_twophase postmaster.pid
The 9.6 version was the same.
The command I use (as user postgres) is:
initdb -D /var/lib/pgsql/10.2/data &
HTH,
Rich
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-22 00:01:24 | Re: initdb when data/ folder has mount points |
| Previous Message | Lucas Fairchild-Madar | 2018-02-21 22:56:43 | Understanding query planner cpu usage |