BUG #18911: Bug in the command INHERITS.

Started by PG Bug reporting form12 months ago7 messagesbugs
Jump to latest
#1PG Bug reporting form
noreply@postgresql.org

The following bug has been logged on the website:

Bug reference: 18911
Logged by: M. BROUSSE
Email address: bm16ch24f@gmail.com
PostgreSQL version: 17.4
Operating system: Windows 10 professional.
Description:

Hello dev, sorry for my english i'm a french GIS user.
I'm actually using PostgreSQL with Postgis in an intership and if I don't do
mistake, I have discover the command INHERITS don't work as we would.
I have done a test with the exemple in the documentation with my data base.
The command gives all columns from the parent table (cities in the exemple)
to the child table ; but attributs aren't given with tables to the child as
we would.
And more strange, if I create attributs by the child table, these attributs
are given to the parent table...
I have already used the Inheritance command before and it was normaly
working.
I don't know if someone have seen the same bug, and I hope I wasn't wrong
and that was normal.
Sorry for possible mistakes and I stay available if you need more details.
Have a good day.

#2David G. Johnston
david.g.johnston@gmail.com
In reply to: PG Bug reporting form (#1)
Re: BUG #18911: Bug in the command INHERITS.

On Monday, May 5, 2025, PG Bug reporting form <noreply@postgresql.org>
wrote:

The following bug has been logged on the website:

Bug reference: 18911
Logged by: M. BROUSSE
Email address: bm16ch24f@gmail.com
PostgreSQL version: 17.4
Operating system: Windows 10 professional.
Description:

Sorry for possible mistakes and I stay available if you need more details.
Have a good day.

Yes, providing the code that demonstrates the bug you are reporting is
basically a requirement for reporting bugs.

David J.

#3David G. Johnston
david.g.johnston@gmail.com
In reply to: PG Bug reporting form (#1)
Re: BUG #18911: Bug in the command INHERITS.

On Mon, May 5, 2025 at 7:46 AM PG Bug reporting form <noreply@postgresql.org>
wrote:

The following bug has been logged on the website:

Bug reference: 18911
Logged by: M. BROUSSE
Email address: bm16ch24f@gmail.com
PostgreSQL version: 17.4
Operating system: Windows 10 professional.
Description:

Based upon an off-list reply I've determined there is no bug here.

David J.

#4M. BROUSSE
bm16ch24f@gmail.com
In reply to: David G. Johnston (#3)
Re: BUG #18911: Bug in the command INHERITS.

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.
Thanks for the help, have a nice day.

#5David G. Johnston
david.g.johnston@gmail.com
In reply to: M. BROUSSE (#4)
Re: BUG #18911: Bug in the command INHERITS.

On Wednesday, May 7, 2025, M. BROUSSE <bm16ch24f@gmail.com> wrote:

I'm a little confused because I already used inheritance on PostgreSQL 16
and attributes were given to children tables.

Show that happening.

David J.

#6Alvaro Herrera
alvherre@2ndquadrant.com
In reply to: M. BROUSSE (#4)
Re: BUG #18911: Bug in the command INHERITS.

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

#7M. BROUSSE
bm16ch24f@gmail.com
In reply to: Alvaro Herrera (#6)
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@kurilemu.de> a écrit :

Show quoted text

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

Attachments:

command inheritance.pngimage/png; name="command inheritance.png"Download