Re: Restriction on table partition expressions

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: James Vanns <jvanns(at)ilm(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Restriction on table partition expressions
Date: 2022-08-25 15:31:53
Message-ID: CAApHDvru49vCpfDhsA=wNe8xNHw4pR5Xi5Nx6z2BmvNJnPp9Gw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 26 Aug 2022 at 03:08, James Vanns <jvanns(at)ilm(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ravi Krishna 2022-08-25 20:53:53 Information_schema.table_constraints
Previous Message David Rowley 2022-08-25 15:25:14 Re: Restriction on table partition expressions