From: Euler Taveira <euler@eulerto.com>
To: 303677365@qq.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18729: update with multiple subpartitions return error: too many range table entries
Date: Mon, 02 Dec 2024 12:37:59 -0300
Message-ID: <14c14680-63a7-41b3-b45a-eff4b4d7e24f@app.fastmail.com> (raw)
In-Reply-To: <18729-9bd4c9ec46c39848@postgresql.org>
References: <18729-9bd4c9ec46c39848@postgresql.org>
On Mon, Dec 2, 2024, at 4:07 AM, PG Bug reporting form wrote:
> UPDATE rqg_table3 T2
> SET c2 = T2.c2 || '该行序号不正确;'
> WHERE NOT EXISTS (
> SELECT NULL
> FROM (
> SELECT c1, c0, c2 AS RIGHT_NUM
> FROM rqg_table3
> ORDER BY c1
> ) T3
> WHERE T3.RIGHT_NUM = T2.c2
> AND T3.c0 = T2.c0
> );
It works for v14+. That's because there were some partitioning improvements. In
particular, the commit 86dc90056 and follow up commits. The release notes
describe it as "Improve the performance of updates and deletes on partitioned
tables with many partitions".
I would say that it is time to move from v13 because it is now the oldest
supported version.
--
Euler Taveira
EDB https://www.enterprisedb.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: euler@eulerto.com, 303677365@qq.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18729: update with multiple subpartitions return error: too many range table entries
In-Reply-To: <14c14680-63a7-41b3-b45a-eff4b4d7e24f@app.fastmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox