Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Achilleas Mantzios <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This
Date: 2023-10-23 17:06:23
Message-ID: 51f4369e3ebde2652709715da3052650e0f1042a.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2023-10-23 17:08:34 Re: Passing enum Parameters to User-defined C-Language Functions
Previous Message Adrian Klaver 2023-10-23 17:00:31 Re: PostgreSQL inheritance vs https://wiki.postgresql.org/wiki/Don%27t_Do_This