Re: Optimize commit performance with a large number of 'on commit delete rows' temp tables

From: feichanghong <feichanghong(at)qq(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Optimize commit performance with a large number of 'on commit delete rows' temp tables
Date: 2024-07-05 19:39:41
Message-ID: tencent_C33A6D3E864C0E393610C69418DFF333DA09@qq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The patch in the attachment, compared to the previous one, adds a threshold for
using the bloom filter. The current ON_COMMITS_FILTER_THRESHOLD is set to 64,
which may not be the optimal value. Perhaps this threshold could be configured
as a GUC parameter?

Best Regards,
Fei Changhong

Attachment Content-Type Size
v1-0001-Optimize-commit-with-temp-tables.patch application/octet-stream 7.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marat Bukharov 2024-07-05 19:43:56 Re: [PATCH] Add min/max aggregate functions to BYTEA
Previous Message Paul Jungwirth 2024-07-05 19:22:31 Re: SQL:2011 application time