Re: immutable function querying table for partitioning - Mailing list pgsql-general

From David G. Johnston
Subject Re: immutable function querying table for partitioning
Date
Msg-id CAKFQuwZSrN5_vXniGJ66sh189X2J+jvWq63UZWrErzT=a2=90Q@mail.gmail.com
Whole thread Raw
In response to immutable function querying table for partitioning  (Vijaykumar Jain <vijaykumarjain.github@gmail.com>)
Responses Re: immutable function querying table for partitioning  (Vijaykumar Jain <vijaykumarjain.github@gmail.com>)
List pgsql-general
On Tuesday, June 15, 2021, Vijaykumar Jain <vijaykumarjain.github@gmail.com> wrote:


--- now since the lookup table is update, a noop update would get new shards for ids and rebalance them accordingly.

test=# update t set id = id ;
UPDATE 25

You probably avoid the complications by doing the above, but the amount of bloat you are causing seems excessive.

I’d suggest an approach where you use the table data to build DDL in a form that does adhere to the limitations described in the documentation instead of building you system upon a lie that your immutable function is actually a stable one.

David J.

pgsql-general by date:

Previous
From: Jehan-Guillaume de Rorthais
Date:
Subject: Re: query issue
Next
From: Vijaykumar Jain
Date:
Subject: Re: immutable function querying table for partitioning