Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This - Mailing list pgsql-general

From Laurenz Albe
Subject Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This
Date
Msg-id 51f4369e3ebde2652709715da3052650e0f1042a.camel@cybertec.at
Whole thread Raw
In response to Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This  (Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>)
Responses Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This
List pgsql-general
On Mon, 2023-10-23 at 19:49 +0300, Achilleas Mantzios wrote:
> Tom Lane wrote:
> > But there are valid use-cases where you
> > actually do want more columns in the child tables than the parent.
>
> also data departmentalization, consolidation, multi-tenancy are fine use
> cases (same # and types of columns), you can't have writable VIEWs with
> UNION, for me inheritance is a fantastic feature that I use with success
> for some very important projects.

Yes, there are valid and interesting use cases, although you have to
search for them.  I am sure it can make an interesting talk.

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This
Next
From: Tom Lane
Date:
Subject: Re: Passing enum Parameters to User-defined C-Language Functions