public inbox for [email protected]  

help / color / mirror / Atom feed

From: Chao Li <[email protected]>
To: Postgres hackers <[email protected]>
Cc: Amit Kapila <[email protected]>
Subject: docs: clarify ALTER TABLE behavior on partitioned tables
Date: Wed, 7 Jan 2026 13:59:28 +0800
Message-ID: <CAEoWx2=mYhCfsnHaN96Qqwq5b0GVS2YgO3zpVqPPRd_iO52wRw@mail.gmail.com> (raw)

--00000000000075ead60647c5ff82
Content-Type: multipart/alternative; boundary="00000000000075ead40647c5ff80"

--00000000000075ead40647c5ff80
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Hackers,

This task is derived from [1], as =E2=80=9CALTER TABLE=E2=80=9D is consider=
ed to exhibit
=E2=80=9Cinconsistent=E2=80=9D behaviors with partitioned tables. From the =
current
documentation of =E2=80=9CALTER TABLE=E2=80=9D, readers won=E2=80=99t get e=
nough information to
form a clear understanding of how these commands behave with partitioned
tables, and this gap needs to be addressed.

I have spent several days verifying sub-commands of =E2=80=9CALTER TABLE=E2=
=80=9D one by
one against partitioned tables from the following points:

1) Does an action on a parent partitioned table propagate to child
partitions?
2) Does a value set on a parent partitioned table get automatically
inherited by newly created partitions?
3) Does =E2=80=9CONLY partitioned-table=E2=80=9D work as the documentation =
states
(preventing propagation)?
4) Can an action be performed on a partitioned table and its children
independently?

view thread (2+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: docs: clarify ALTER TABLE behavior on partitioned tables
  In-Reply-To: <CAEoWx2=mYhCfsnHaN96Qqwq5b0GVS2YgO3zpVqPPRd_iO52wRw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox