On Fri, Feb 13, 2026 at 12:34 AM Jim Jones <[email protected]> wrote: > > > > On 12/02/2026 16:08, Fujii Masao wrote: > > On Thu, Feb 12, 2026 at 11:36 PM Matheus Alcantara > > <[email protected]> wrote: > >> The patch fix the issue and it seems correct to me. > > Thanks for the review! > > > The documentation [1] states that INCLUDING COMMENTS copies comments for > > the copied columns, constraints, and indexes. It does not mention copying > > comments on the table itself. Therefore, not copying table comments with > > INCLUDING COMMENTS does not appear to be a bug. That is, the proposed patch > > seems more like an improvement than a bug fix. > > Hmm, it seemed so obvious to me that I didn’t look more closely at the > documentation :) Although I struggle to see the rationale for not > copying a table’s comment in a CREATE TABLE LIKE ... INCLUDING COMMENTS > statement, I have to agree that the documentation is quite clear about > this limitation, and therefore it cannot really be considered a bug. > That said, it may well be worth considering for a future release. > > What are your thoughts?
At first, I felt it would be more intuitive to copy the table comment as well. However, on second thought, since LIKE can reference multiple tables, copying table-level properties such as comments may not be well-defined. For example, if two source tables each have a table comment and both are specified in LIKE, which comment should be applied to the new table? Regards, -- Fujii Masao
