Re: BUG #18911: Bug in the command INHERITS.

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: "M(dot) BROUSSE" <bm16ch24f(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18911: Bug in the command INHERITS.
Date: 2025-05-07 14:59:33
Message-ID: 202505071459.cwnqhmwv2ubj@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2025-May-07, M. BROUSSE wrote:

> I'm a little confused because I already used inheritance on PostgreSQL 16
> and attributes were given to children tables. So, is it normal that
> attributes aren't given to children, if you said so.

Please explain what you mean by "attributes". Most people here
consider "attribute" to be a synonym for "column", but I noticed that
you used both the terms in your first email as if you meant two
different things.

It helps if you show the exact commands you run (to create the
parent/child tables in an empty database), the output you get, and
explain how that output differs from the output you expect.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"You don't solve a bad join with SELECT DISTINCT" #CupsOfFail
https://twitter.com/connor_mc_d/status/1431240081726115845

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Junwang Zhao 2025-05-07 15:35:26 Re: Incorrect calculation of path fraction value in MergeAppend
Previous Message David G. Johnston 2025-05-07 13:33:51 Re: BUG #18911: Bug in the command INHERITS.