MIME-Version: 1.0
References: <ZkN6EfjQGz8TOhbL@pryzbyj2023>
 <CAPpHfdvz3S7SoRiaSk9C-Juy2EzHs6NC_c9uUR0i7bymKXkvuQ@mail.gmail.com>
 <ai_c4-v8iLA2kXFV@pryzbyj2023>
 <CAPpHfdvOvaPxMoUp3T6hf4UmAaOhdPCcw71OGUWDjTXvrTZ_JA@mail.gmail.com>
 <CALT9ZEFrDgha=RyOuWru45FTk9Dbj5FF-fTw0NnE8n1FwBb2yg@mail.gmail.com>
 <CAPpHfdvpzvNt=d_Csxe-TCtvF9MRNdeMtfJu3RkmTgBkkQbGUw@mail.gmail.com>
 <CALT9ZEG0YmzH+3M6PixHUNq13pYt+yh8sAgonfaut=g_ij=oZw@mail.gmail.com>
 <CAPpHfdtVp5Xxz59Zse+Gg_oWvZPpwjr+gcVtWq-5pTp0Rsh8gQ@mail.gmail.com>
 <CALT9ZEG39=w6zvDqpKc479WjmeNGFMwdJxi=Ut7z4JUN386URg@mail.gmail.com>
 <CAPpHfdte=WJQnEnEhf8cKZYE1rT-VfQ2mgh=1dCsCCdSYStSow@mail.gmail.com>
 <ajQTklv8QArzTp3h@pryzbyj2023>
 <CAPpHfduZ9Yd6vG0EOZUa_MOVxpEDMsZB-89pgNypwFzp2ax+NQ@mail.gmail.com>
In-Reply-To: 
 <CAPpHfduZ9Yd6vG0EOZUa_MOVxpEDMsZB-89pgNypwFzp2ax+NQ@mail.gmail.com>
From: Pavel Borisov <pashkin.elfe@gmail.com>
Date: Mon, 22 Jun 2026 14:44:33 +0400
Message-ID: 
 <CALT9ZEE9=LbuNx6t1duyXpRx7OM7W5NLirK+5b+8zzV8QrYDmw@mail.gmail.com>
Subject: Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>,
 Dmitry Koval <d.koval@postgrespro.ru>,
	Alexander Lakhin <exclusion@gmail.com>, pgsql-hackers@lists.postgresql.org,
	Tomas Vondra <tomas.vondra@enterprisedb.com>,
 Alvaro Herrera <alvherre@alvh.no-ip.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CALT9ZEE9%3DLbuNx6t1duyXpRx7OM7W5NLirK%2B5b%2B8zzV8QrYDmw%40mail.gmail.com>
Precedence: bulk

Hi, Alexander!

On Sun, 21 Jun 2026 at 16:11, Alexander Korotkov <aekorotkov@gmail.com> wro=
te:
>
> On Thu, Jun 18, 2026 at 6:49=E2=80=AFPM Justin Pryzby <pryzby@telsasoft.c=
om> wrote:
> > On Thu, Jun 18, 2026 at 10:31:11AM +0300, Alexander Korotkov wrote:
> > > Pushed with your suggestions accepted.
> >
> > Thanks.  When I went back to test this, I merged ~25 partitions that
> > were all on the same tablespace, but the merged table was created on th=
e
> > default tablespace.
> >
> > I tried again with default_tablespace set, but it was ignored.  I think
> > that's wrong.  It's good to follow the tablespace of the parent table,
> > but if it has no tablespace set, default_tablespace should be obeyed.
> > See surrounding logic in DefineRelation.
> >
> > I see the docs say this:
> > +       <command>ALTER TABLE MERGE PARTITION</command> uses the partiti=
oned
> > +       table itself as the template to construct the new partition.
> > +       The new partition will inherit the same table access method, pe=
rsistence
> > +       type, and tablespace as the partitioned table.
>
> Correct, please see the attached patch, it makes
> createPartitionTable() deal with tablespaces the same was as
> DefineRelation() does.

Thank you for working on this feature!
I've looked into the last v1 patch.

Does it also worth inheriting DefineRelation()'s check and error for
the case if (tablespaceId =3D=3D GLOBALTABLESPACE_OID)?
A brief look for default_tablespace GUC doesn't reveal a way why it
could not be set to global tablespace in a session.

Best regards,
Pavel Borisov
Supabase