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

feichanghong <feichanghong@qq.com>

From: feichanghong <feichanghong@qq.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>

Date: 2024-07-05T19:39:41Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Lift limitation that PGPROC->links must be the first field
- 98347b5a3ab1 18.0 cited

Attachments

v1-0001-Optimize-commit-with-temp-tables.patch (application/octet-stream) patch v1-0001

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