Re: Plans for partitioning of inheriting tables - Mailing list pgsql-general

From thiemo@gelassene-pferde.biz
Subject Re: Plans for partitioning of inheriting tables
Date
Msg-id 20241101201600.Horde.Br4fPP8BFAAwzFoMaM8_eJS@webmail.gelassene-pferde.biz
Whole thread Raw
In response to Re: Plans for partitioning of inheriting tables  (Torsten Förtsch <tfoertsch123@gmail.com>)
Responses Re: Plans for partitioning of inheriting tables
List pgsql-general

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.


pgsql-general by date:

Previous
From: thiemo@gelassene-pferde.biz
Date:
Subject: Re: Plans for partitioning of inheriting tables
Next
From: Adrian Klaver
Date:
Subject: Re: Plans for partitioning of inheriting tables