Message-ID: <a55b608844e040ffaa89df481c0ed9e76603b1e8.camel@cybertec.at>
Subject: Re: BUG #19051: Is it possible to move a TOAST table to a different
 tablespace than its parent table?
From: Laurenz Albe <laurenz.albe@cybertec.at>
Mail-Followup-To: pgsql-general@lists.postgresql.org
Mail-Reply-To: pgsql-general@lists.postgresql.org
To: mhararci@gmail.com, pgsql-bugs@lists.postgresql.org
Date: Sun, 14 Sep 2025 12:29:09 +0200
In-Reply-To: <19051-90b4476ef19f9b73@postgresql.org>
References: <19051-90b4476ef19f9b73@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-2.fc42) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/a55b608844e040ffaa89df481c0ed9e76603b1e8.camel%40cybertec.at>
Precedence: bulk

On Sun, 2025-09-14 at 09:17 +0000, PG Bug reporting form wrote:
> I'm currently using PostgreSQL 16.10 and I've run into a challenge regard=
ing
> moving TOAST data for a table. My goal is to have the TOAST data for a
> column stored in a different tablespace from the parent table.
>=20
> Specifically, I have a users table with a profile_data column of type JSO=
NB,
> which can contain large objects. I want the users table itself to reside =
in
> the ts_medium_data tablespace, while its associated TOAST data is stored =
in
> a separate ts_medium_toast tablespace.

Don't write to the bugs mailing list if you need help.
I have directed replies to the -general mailing list.

You won't be able to put a table and its TOAST table into different tablesp=
aces.

But there wouldn't be any benefit in doing that anyway, so that
is no problem.  Perhaps you could detail the *real problem* you are trying
to solve...

Yours,
Laurenz Albe