Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vfJ6P-000pJf-0t for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Jan 2026 14:41:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vfJ5P-000eI9-1P for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Jan 2026 14:40:03 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vfJ5P-000eI1-0U for pgsql-hackers@lists.postgresql.org; Mon, 12 Jan 2026 14:40:03 +0000 Received: from mail-ot1-x335.google.com ([2607:f8b0:4864:20::335]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vfJ5N-0002FS-0D for pgsql-hackers@lists.postgresql.org; Mon, 12 Jan 2026 14:40:02 +0000 Received: by mail-ot1-x335.google.com with SMTP id 46e09a7af769-7c7613db390so3970041a34.2 for ; Mon, 12 Jan 2026 06:40:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1768228801; x=1768833601; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=XwE0Fg3VPcrHUGFYBZDXi6/DjUKW1QKutR8ZFHGD+gw=; b=DOdAMByiIQmNK6uo37w9Qsswm4y0qoCaIY50mPFHRq6weGw4NFRuh3spsRwzGobHQZ 16jjwdYfieNwKdGlG++wBv5jskkwzqVxgLH5Gn5DMjxP9Sx7Xuvst9zGwdCtiLPLSYrQ F6/39/s3BE9yx5eUoq8Og1M/qL7gZIWrxSmxjOfrZvHtE7Iyk7PG4I3q6OWs5EkE+o2L ls6avFFXTGcJ0DwgkIiUxtpSuBSS3JIRcP3rsP7jmQyc6f48xlCnNuInkgjdfSlQ3bml 9uVJdP4L6EAIEkuiqg41uxl9iEld0yK2tvlD9sDzP7wp/gk0jjF0KHCf/SLaG1sT38bH C0QQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768228801; x=1768833601; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=XwE0Fg3VPcrHUGFYBZDXi6/DjUKW1QKutR8ZFHGD+gw=; b=pfR/VIner86/f+TmNRKwgiG+ZkjV+V/Or7NY8NDjFaFq5b83/u54TVey+8PpeLIFyJ +jQx4fyS2UdrYM5iSAU9VTF8pZheCZN+ODjhTMFu2CiintfWi9+HO9NBOOrZwoL/oXq1 n2IHjMp472+MbZhcTJ+8xypBtUYLccT1EySoMKSMmSsxRpBJLwEbIKVA5IQpKd2IkgYL JAQrJXG0nSazE6FPiViHK1llW1ENSGIdfdp6lKe1Y8VA4FTw3RzWSW9vckya1uJsb54s fvpNktS0lOS4gREwS2Kzon/QCAESbRPlhPd1UKSPWkSH9b6Ui1WMt9Onr6lD99CfL0Ul 2X9Q== X-Gm-Message-State: AOJu0YytTmtNQoC42PaeyqhECr/4a+/bcSWD07iQxZI/sugvewwX9/nG OzMSQl4zx9JtPzwaR4uyDkpMCsHp5P+2f5VE8ht5PbIcXKG7BNLW/ZXT3F5e2kQIIVauEAqkUL8 3qzBx6zpmqYBM8Y0OK8k+Mnnvqo0Gkcw= X-Gm-Gg: AY/fxX6g7QmQ2JExoeDdh5eK6eD3iE1qeRolvxjTDJgfPuztJ8tBx/YbfZGkJ86BXv1 Yo7XW1j3w/AW/iO+lY28CdoH9dNS+SG8FXuEofGCZG5YbUSuOI+YiT6FhFk3oGuFC1/dkXSnB6G EG6qxlnS4EMi0v8ur2dRgJGsrL+9BHMeJmQv4QojNE4mOUBpD5z3v0cbkd4NdjNYi0kEq2vlm7N aNdG1Csowa/rXNO8+2aUp0Vw/dSjmzSwNUQBYsHcF4rBP/GSVfYbprY0vaQWaX42FWXfd0M X-Google-Smtp-Source: AGHT+IFra78O53OBVkx6l4UjvYmoTy/ozY9dUOWoXsaeFNZDn8JRTiSWQKEz3bwtVMQ5PUmFiF++yGY7avyVE+Y2l4Q= X-Received: by 2002:a4a:be9a:0:b0:65f:5869:f7e7 with SMTP id 006d021491bc7-65f5869fddemr6430157eaf.63.1768228800974; Mon, 12 Jan 2026 06:40:00 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a05:6802:6649:10b0:619:571f:707d with HTTP; Mon, 12 Jan 2026 06:40:00 -0800 (PST) In-Reply-To: References: From: "David G. Johnston" Date: Mon, 12 Jan 2026 07:40:00 -0700 X-Gm-Features: AZwV_QiiIqQz81Xbid91NVTR1ouVub8GFxTKOJtv-2pNnC_SQwRkaXZQlRMBlNU Message-ID: Subject: Re: ALTER TABLE: warn when actions do not recurse to partitions To: Chao Li Cc: Postgres hackers Content-Type: multipart/alternative; boundary="000000000000905507064831d931" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000905507064831d931 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Monday, January 12, 2026, Chao Li wrote: > > For now, I=E2=80=99ve limited the change to REPLICA IDENTITY to see wheth= er there > are objections to this approach. If there are none, I plan to extend the > same warning behavior to the other sub-commands listed above. After that, > users can reasonably assume that an ALTER TABLE partitioned_table > ... action will recurse to child partitions unless a warning explicitly > tells them otherwise. > It should be a notice, not a warning. 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? David J. --000000000000905507064831d931 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Monday, January 12, 2026, Chao Li <li.evan.chao@gmail.com> wrote:

For now, I=E2=80=99ve limited the change to=C2=A0RE= PLICA IDENTITY=C2=A0to see whether there are objections to this approach. I= f there are none, I plan to extend the same warning behavior to the other s= ub-commands listed above. After that, users can reasonably assume that an= =C2=A0ALTER TABLE partitioned_table ...=C2=A0action will recurse to child p= artitions=C2=A0unless=C2=A0a warning explicitly tells them otherwise.
=

It should be a notice, not a w= arning.

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

David= J.

--000000000000905507064831d931--