Re: BUG #15954: Unable to alter partitioned table to set logged

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, "keith(dot)fiske(at)crunchydata(dot)com" <keith(dot)fiske(at)crunchydata(dot)com>, "ejberdecia(at)yahoo(dot)com" <ejberdecia(at)yahoo(dot)com>, "david(dot)rowley(at)2ndquadrant(dot)com" <david(dot)rowley(at)2ndquadrant(dot)com>, "amitlangote09(at)gmail(dot)com" <amitlangote09(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15954: Unable to alter partitioned table to set logged
Date: 2024-04-24 07:24:19
Message-ID: Ziizo3ML2KwsuE9U@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Apr 23, 2024 at 05:33:00AM -0700, David G. Johnston wrote:
> Correct, it is an outright bug that I see no reason not to just fix and
> back-patch. The new feature needs its own thread so as not to have this
> one see the same fate it had 5 years ago.

The semantics have become much more complicated than 5 years ago
because partitioned tables have gained support for more things, one
being the recent addition of identity columns. While I've analyzed
the whole, I have asked myself a couple of questions about what the
best user-friendly behavior would be, implemented one and mentioned
the rest. Anyway, a new thread has been created about this topic, so
feel free to reply there:
https://www.postgresql.org/message-id/ZiiyGFTBNkqcMQi_%40paquier.xyz
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Lakhin 2024-04-24 13:00:00 Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
Previous Message Kostiantyn Tomakh 2024-04-24 06:03:32 Re: BUG #18433: Logical replication timeout