Re: partition pruning only works for select but update

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: partition pruning only works for select but update
Date: 2022-07-01 13:18:28
Message-ID: 712769.1656681508@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> On Fri, Jul 01, 2022 at 08:30:40AM +0000, James Pang (chaolpan) wrote:
>> We have other application depend on V13, possible to backport code changes to V13 as https://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=86dc90056dfdbd9d1b891718d2e5614e3e432f35

> In any case, I'm sure the feature won't be backpatched to v13 - it's an
> improvement but not a bugfix.

Even more to the point, it was an extremely major change and would take
a huge amount of QA effort to ensure that dropping it into v13 wouldn't
cause fresh problems. The PG community has exactly no interest in making
such effort.

Besides which, what do you imagine "depends on v13" actually means?
If you have an app that works on v13 but not v14, maybe it's because
it depends on the old behavior in some way.

Spend your effort on updating your app, instead.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message James Pang (chaolpan) 2022-07-01 14:06:11 RE: partition pruning only works for select but update
Previous Message Justin Pryzby 2022-07-01 13:13:11 Re: partition pruning only works for select but update