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:14:08 |
Message-ID: | 20241101201408.Horde.O-JA4FN6beZ7-GZi4ySiKnQ@webmail.gelassene-pferde.biz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> escribió:
> Even if there where plans, any changes would happen in the future
> and would not be help the now problem.
Yes and no. I can live without the partitioning, as I do not intend to
load data from more than one source. Other might. But until others
want to load data from different sources, a comment in the source
might do that partitioning of inheriting tables will be supported in
the future. But, that is an academic point now.
> That is contradicted by your statement below:
>
> Either performance is important or it is not.
Not quite. If the performance penalty by suboptimal choice in
partitioning does not matter in the current project because the
raster/bytea stuff does affect performance much more, it does not mean
that I cannot work on other project where it can matter. And even if
the latter is not the case, I can be just curious about it.
> If TILE is referring to the same thing you are dealing with in
> related question on psycopg list then you are talking about bytea
> storage. You should take a look at:
>
> https://www.postgresql.org/docs/current/storage-toast.html
Indeed, it does. Thanks for the hint.
From | Date | Subject | |
---|---|---|---|
Next Message | thiemo | 2024-11-01 19:16:00 | Re: Plans for partitioning of inheriting tables |
Previous Message | Torsten Förtsch | 2024-11-01 18:43:33 | Re: Plans for partitioning of inheriting tables |