Re: ALTER TABLE: warn when actions do not recurse to partitions

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: ALTER TABLE: warn when actions do not recurse to partitions
Date: 2026-01-12 15:23:11
Message-ID: CAKAnmm+A=b=UrLJzwAtRo8ZgjaJWDR1SAGKg8-vu0a98YUnURg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 12, 2026 at 9:40 AM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> How about indicating how many partitions were affected in the notice and
> allowing the absence of such a notice to be the indicator that cascading
> did not happen?
>

I like the idea of number of partitions, but think we need to be more
explicit than people surmising the lack of a notice is significant.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2026-01-12 15:36:55 Re: typedef indentation in pg_shmem.h
Previous Message Jim Jones 2026-01-12 15:17:31 Re: [PATCH] psql: add \dcs to list all constraints