Re: Restriction on table partition expressions

David Rowley <dgrowleyml@gmail.com>

From: David Rowley <dgrowleyml@gmail.com>
To: James Vanns <jvanns@ilm.com>
Cc: pgsql-general@lists.postgresql.org
Date: 2022-08-25T15:31:53Z
Lists: pgsql-general
On Fri, 26 Aug 2022 at 03:08, James Vanns <jvanns@ilm.com> wrote:
> Also, is there a chance that this
> limitation will be relaxed in the future?

(forgot to answer this part)

Certainly not in the near future, I'm afraid.  It would require
allowing a single index to exist over multiple tables. There has been
discussions about this in the past and the general thoughts are that
if you have a single index over all partitions, then it massively
detracts from the advantages of partitioning.  With partitioning, you
can DETACH or DROP a partition and get rid of all the data quickly in
a single metadata operation.  If you have an index over all partitions
then that operation is no longer a metadata-only operation. It
suddenly needs to go and remove or invalidate all records pointing to
the partition you want to detach/drop.

David



Commits

  1. Doc: clarify partitioned table limitations