public inbox for [email protected]  

help / color / mirror / Atom feed

From: Thiemo Kellner <[email protected]>
To: PostgreSQL General <[email protected]>
Subject: Re: Plans for partitioning of inheriting tables
Date: Fri, 1 Nov 2024 21:47:37 +0100 (GMT+01:00)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<20241101094106.Horde.TwPSs9YUgJ5v-_M-4ltwoeh@webmail.gelassene-pferde.biz>
	<[email protected]>
	<20241101182110.Horde.P_w6KptTjJNeM1X9Asg5bE3@webmail.gelassene-pferde.biz>
	<[email protected]>
	<CAKkG4_nV-+6rz-01pA-S5vD7ai2h_ujF1cDFoOBG10CCHgRfmg@mail.gmail.com>
	<20241101201600.Horde.Br4fPP8BFAAwzFoMaM8_eJS@webmail.gelassene-pferde.biz>
	<[email protected]>

It looks to me basically to be a "create table A as select * from B where false".

01.11.2024 20:38:15 Adrian Klaver <[email protected]>:

> On 11/1/24 12:16, [email protected] wrote:
>> 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.
> 
> Not sure what you mean by structural copy, but the table created by CREATE TABLE LIKE will not have any association with the table it was created from.
> 
> https://www.postgresql.org/docs/current/sql-createtable.html
> 
> "Unlike INHERITS, the new table and original table are completely decoupled after creation is complete. Changes to the original table will not be applied to the new table, and it is not possible to include data of the new table in scans of the original table."
> 
>> Torsten Förtsch <[email protected] <mailto:[email protected]>> 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.
>> 
> 
> -- 
> Adrian Klaver
> [email protected]

view thread (13+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Plans for partitioning of inheriting tables
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox