Received-SPF: pass (ha01s018.org-dns.com: connection is authenticated)
Date: Fri, 01 Nov 2024 20:16:00 +0100
Message-ID: 
 <20241101201600.Horde.Br4fPP8BFAAwzFoMaM8_eJS@webmail.gelassene-pferde.biz>
From: thiemo@gelassene-pferde.biz
To: PostgreSQL General <pgsql-general@lists.postgresql.org>
Subject: Re: Plans for partitioning of inheriting tables
References: <ea963edb-5437-4de6-bd2c-97c141a391b8@gelassene-pferde.biz>
 <5757acdc-39ed-4642-a449-26e47b1bcf95@gelassene-pferde.biz>
 <d9d6a2f4-379b-45f3-9005-ab047625c1a4@aklaver.com>
 <20241101094106.Horde.TwPSs9YUgJ5v-_M-4ltwoeh@webmail.gelassene-pferde.biz>
 <14c1eb8c-a853-43b3-a1ea-b105bfd6c99b@aklaver.com>
 <20241101182110.Horde.P_w6KptTjJNeM1X9Asg5bE3@webmail.gelassene-pferde.biz>
 <6bc57377-52e1-496a-b9d6-4cd9dc84d92e@aklaver.com>
 <CAKkG4_nV-+6rz-01pA-S5vD7ai2h_ujF1cDFoOBG10CCHgRfmg@mail.gmail.com>
In-Reply-To: 
 <CAKkG4_nV-+6rz-01pA-S5vD7ai2h_ujF1cDFoOBG10CCHgRfmg@mail.gmail.com>
Accept-Language: de
Content-Type: multipart/alternative; boundary="=_sn2kdYq_OXLYGM_VCFywDGZ"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/20241101201600.Horde.Br4fPP8BFAAwzFoMaM8_eJS%40webmail.gelassene-pferde.biz>
Precedence: bulk

This message is in MIME format.

--=_sn2kdYq_OXLYGM_VCFywDGZ
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
Content-Description: =?utf-8?b?U8OzbG8=?= texto
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

  Thanks, I shall have a look into it. I was under the assumption the  
the create table like would create no more than a structural copy.

Torsten F��rtsch <tfoertsch123@gmail.com> escribi��:

> Thiemo,      ��
>    it looks to me like you are using inheritance just to make sure  
> your SOURCES and TOPO_FILES tables have some common columns. If you  
> are not actually querying the TEMPLATE_TECH table and expect to see  
> all the rows from the other 2 tables in that one table combined,  
> then you could use CREATE TABLE (LIKE ...) instead of inheritance.  
> That way your "child" tables would become normal tables and you  
> could use declarative partitioning on them.
>    ��
>    Even if you are querying the TEMPLATE_TECH table, you could still  
> do that by turning the TEMPLATE_TECH table into a view which  
> performs a UNION ALL over the other tables.

--=_sn2kdYq_OXLYGM_VCFywDGZ
Content-Type: text/html; charset=utf-8
Content-Description: Mensaje HTML
Content-Disposition: inline

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title></title>
</head>
<body style="font-family:Arial;font-size:14px">
<p>Thanks, I shall have a look into it. I was under the assumption the the create table like would create no more than a structural copy.<br>
<br>
Torsten F&ouml;rtsch &lt;<a href="mailto:tfoertsch123@gmail.com">tfoertsch123@gmail.com</a>&gt; escribi&oacute;:</p>
<blockquote style="border-left:2px solid blue;margin-left:2px;padding-left:12px;" type="cite">
<div dir="ltr">Thiemo,
<div>&nbsp;</div>
<div>it looks to me like you are using inheritance just to make sure your SOURCES and TOPO_FILES tables have some common columns. If you are not actually querying the TEMPLATE_TECH table and expect to see all the rows from the other 2 tables in that one table combined, then you could use CREATE TABLE (LIKE ...) instead of inheritance. That way your "child" tables would become normal tables and you could use declarative partitioning on them.</div>
<div>&nbsp;</div>
<div>Even if you are querying the TEMPLATE_TECH table, you could still do that by turning the TEMPLATE_TECH table into a view which performs a UNION ALL over the other tables.</div>
</div>
</blockquote>
<p><br type="_moz"></p>
</body>
</html>
--=_sn2kdYq_OXLYGM_VCFywDGZ--