From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Creating a new database on a different file system |
Date: | 2025-03-17 18:33:52 |
Message-ID: | CANzqJaCZH2KmjOpAWXA=jUb-+He0D68sgY-YTibjk4bmH5Qt0A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Mar 17, 2025 at 11:18 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> On Mon, 2025-03-17 at 15:51 +0100, Luca Ferrari wrote:
> > On Mon, Mar 17, 2025 at 3:49 PM Ian Dauncey <Ian(dot)Dauncey(at)bankzero(dot)co(dot)za>
> wrote:
> > > We have created a few databases on the file system defined in the
> postgresql.conf,
> > > but now I would like to create another database within the same
> cluster but on a
> > > different file system.
> > >
> > > Is this possible and if so, how do we go about it.
> >
> > create a tablespace on the filesystem you want to use, and then create
> > the database adding the `WITH TABLESPACE` clause.
> > See <https://www.postgresql.org/docs/17/sql-createtablespace.html>
>
> That is an option, but I would recommend to create a new database cluster
> on the new file system rather than creating a tablespace.
>
That of course requires using another port, which can be tricky in a
company that by default closes all firewall ports at the network switch
level, and where you must enumerate every server/subnet ("Rejected. Subnet
range too broad!") that needs access to the new port, it takes time for
requests for new port openings to be approved ("Rejected. We don't
recognize 5433!") and then implemented.
Much easier to use a tablespace.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2025-03-17 19:17:26 | Re: #1 - Known bug (memory related) with respect to Aurora postgresql 13.16.3 |
Previous Message | Tom Lane | 2025-03-17 15:29:36 | Re: Restoring only a subset of schemas |