Content-Type: multipart/alternative;
 boundary="------------60UU9tFJkaBV2fl7RtgNeotx"
Message-ID: <c5c3bb5c-b24a-4712-87f8-9650bfff6462@cloud.gatewaynet.com>
Date: Fri, 1 Nov 2024 16:15:54 +0100
MIME-Version: 1.0
Subject: Re: Plans for partitioning of inheriting tables
To: pgsql-general@lists.postgresql.org
References: <20241024214702.Horde.hYZQZgT8lc-DKEIqL9Ai-E3@webmail.gelassene-pferde.biz>
 <CAKFQuwY0F7xvOzM3q4-bm1XaJisrKWE9Jdu5ZPHCvY1UBFKn9Q@mail.gmail.com>
Content-Language: en-US
From: Achilleas Mantzios - cloud <a.mantzios@cloud.gatewaynet.com>
In-Reply-To: <CAKFQuwY0F7xvOzM3q4-bm1XaJisrKWE9Jdu5ZPHCvY1UBFKn9Q@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/c5c3bb5c-b24a-4712-87f8-9650bfff6462%40cloud.gatewaynet.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------60UU9tFJkaBV2fl7RtgNeotx
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit


On 10/24/24 21:58, David G. Johnston wrote:
> On Thursday, October 24, 2024, <thiemo@gelassene-pferde.biz> wrote:
>
>
>     Up to version 17, partitioning of tables inheriting from other
>     tables is not possible.
>
>         psql:../code_files/data_storage/PostgreSQL/tables/TOPO_FILES.pg_sql:68:
>         ERROR:  no se puede crear una tabla particionada como hija de
>         herencia
>
>
>     Are there plans to support this in the future? I could not find
>     any hint in the documentation or in
>     https://wiki.postgresql.org/wiki/Development_information
>     <https://wiki.postgresql.org/wiki/Development_information>.
>
>
> My impression of things is that directly using “inherit” for table 
> creation is considered deprecated at this point.  No one has interest 
> in expanding on the feature nor even recommends it be used in new 
> development.  That particular unique feature of PostgreSQL hasn’t 
> caught on.
Hi, opinions vary, IMHO inheritance it is a nice feature to have 
especially in multi-tenant situation where tenants represent a division 
or subsidiary rather than a completely foreign entity which should live 
in total isolation, plus the ability to have data on the top owning or 
managing organization. IMHO nothing beats inheritance in fitting to the 
above model. Partitioning comes close but partitioned tables cannot have 
any data on their own. There are workarounds of course to that, but they 
don't fit like a glove. But again I have not tested in heavy xactional 
envs TBT, I am just saying the feature is handy for many applications 
and models. I use it personally in my company and love it. Could I do 
without it? of course, but it would be ugly.
>
> David J.
--------------60UU9tFJkaBV2fl7RtgNeotx
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 10/24/24 21:58, David G. Johnston
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKFQuwY0F7xvOzM3q4-bm1XaJisrKWE9Jdu5ZPHCvY1UBFKn9Q@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      On Thursday, October 24, 2024, &lt;<a
        href="mailto:thiemo@gelassene-pferde.biz" moz-do-not-send="true"
        class="moz-txt-link-freetext">thiemo@gelassene-pferde.biz</a>&gt;
      wrote:<br>
      <blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
        Up to version 17, partitioning of tables inheriting from other
        tables is not possible.<br>
        <blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
          psql:../code_files/data_storag<wbr>e/PostgreSQL/tables/TOPO_<wbr>FILES.pg_sql:68:
          ERROR:  no se puede crear una tabla particionada como hija de
          herencia<br>
        </blockquote>
      </blockquote>
    </blockquote>
    <blockquote type="cite"
cite="mid:CAKFQuwY0F7xvOzM3q4-bm1XaJisrKWE9Jdu5ZPHCvY1UBFKn9Q@mail.gmail.com">
      <blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
        Are there plans to support this in the future? I could not find
        any hint in the documentation or in <a
href="https://wiki.postgresql.org/wiki/Development_information"
          target="_blank" moz-do-not-send="true">https://wiki.postgresql.org/wi<wbr>ki/Development_information</a>.<br>
      </blockquote>
      <div><br>
      </div>
      <div>My impression of things is that directly using “inherit” for
        table creation is considered deprecated at this point.  No one
        has interest in expanding on the feature nor even recommends it
        be used in new development.  That particular unique feature of
        PostgreSQL hasn’t caught on.</div>
    </blockquote>
    Hi, opinions vary, IMHO inheritance it is a nice feature to have
    especially in multi-tenant situation where tenants represent a
    division or subsidiary rather than a completely foreign entity which
    should live in total isolation, plus the ability to have data on the
    top owning or managing organization. IMHO nothing beats inheritance
    in fitting to the above model. Partitioning comes close but
    partitioned tables cannot have any data on their own. There are
    workarounds of course to that, but they don't fit like a glove. But
    again I have not tested in heavy xactional envs TBT, I am just
    saying the feature is handy for many applications and models. I use
    it personally in my company and love it. Could I do without it? of
    course, but it would be ugly. <br>
    <blockquote type="cite"
cite="mid:CAKFQuwY0F7xvOzM3q4-bm1XaJisrKWE9Jdu5ZPHCvY1UBFKn9Q@mail.gmail.com">
      <div><br>
      </div>
      <div>David J.</div>
      <div> </div>
    </blockquote>
  </body>
</html>

--------------60UU9tFJkaBV2fl7RtgNeotx--