From: | Sam Stearns <sam(dot)stearns(at)dat(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Alternate Datafile Location |
Date: | 2024-08-29 23:55:59 |
Message-ID: | CAN6TVjn50xywz0qKcVhra1GFmYF0n1g4s7gdBVMdUr1Dpt9cng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ok, we were going with the approach of the Postgres software (cluster)
being on the root filesystem then creating databases with data file storage
on an alternate filesystem.
It's sounding like the better approach would be to install the Postgres
software (cluster with initdb) on a filesystem other than root. Do I have
that right?
On Fri, Aug 30, 2024 at 9:17 AM Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:
> You should take a step back and read the basic documentation on PG
> administration. For instance:
> https://www.postgresql.org/docs/16/creating-cluster.html
>
> We (at least I) have been assuming that you wanted to create a new
> database cluster, to run a server against that storage, using initdb. Using
> an already running server to put data elsewhere, using createdb is
> different, and requires that you create a tablespace first:
> https://www.postgresql.org/docs/16/manage-ag-tablespaces.html
>
>
--
*Samuel Stearns*
Lead Database Administrator
*c:* 971 762 6879 | *o:* 503 672 5115 | DAT.com
[image: DAT]
<https://www.dat.com/?utm_medium=email&utm_source=DAT_email_signature_link>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2024-08-30 00:14:28 | Re: Alternate Datafile Location |
Previous Message | Scott Ribe | 2024-08-29 23:47:22 | Re: Alternate Datafile Location |