Re: Optimize commit performance with a large number of 'on commit delete rows' temp tables - Mailing list pgsql-hackers

From feichanghong
Subject Re: Optimize commit performance with a large number of 'on commit delete rows' temp tables
Date
Msg-id tencent_C33A6D3E864C0E393610C69418DFF333DA09@qq.com
Whole thread Raw
In response to Re: Optimize commit performance with a large number of 'on commit delete rows' temp tables  (feichanghong <feichanghong@qq.com>)
Responses Re: Optimize commit performance with a large number of 'on commit delete rows' temp tables
List 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

pgsql-hackers by date:

Previous
From: Paul Jungwirth
Date:
Subject: Re: SQL:2011 application time
Next
From: Marat Bukharov
Date:
Subject: Re: [PATCH] Add min/max aggregate functions to BYTEA