Re: immutable function querying table for partitioning

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: immutable function querying table for partitioning
Date: 2021-06-15 12:51:27
Message-ID: CAKFQuwZSrN5_vXniGJ66sh189X2J+jvWq63UZWrErzT=a2=90Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tuesday, June 15, 2021, Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vijaykumar Jain 2021-06-15 13:26:39 Re: immutable function querying table for partitioning
Previous Message Jehan-Guillaume de Rorthais 2021-06-15 11:41:51 Re: query issue