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

For creating the parents and child tables I used the same command as the
exemple in the documentation (like the picture attached to the mail).
I expected from the inheritance to give all information inside the parent
table to the child table, but obviously I was wrong.
And sorry but like I said in my previous email, I don't have anymore my
project where I used the same command and where I had doubts.

Don't worry for me, I asked because I thought it was a bug and I was
searching for a method for creating an exact copy of an existing table.
Don't waste your time for my mistake, I was just wrong.
Thank you so much for explaining and taking your time for me.
Have a nice day, sincerely.

Le mer. 7 mai 2025 à 17:00, Álvaro Herrera <alvherre(at)kurilemu(dot)de> a écrit :

> 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
>