From: | thiemo(at)gelassene-pferde(dot)biz |
---|---|
To: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Plans for partitioning of inheriting tables |
Date: | 2024-11-01 19:16:00 |
Message-ID: | 20241101201600.Horde.Br4fPP8BFAAwzFoMaM8_eJS@webmail.gelassene-pferde.biz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)gmail(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-11-01 19:38:09 | Re: Plans for partitioning of inheriting tables |
Previous Message | thiemo | 2024-11-01 19:14:08 | Re: Plans for partitioning of inheriting tables |