Re: brininsert optimization opportunity

Tomas Vondra <tomas.vondra@enterprisedb.com>

From: Tomas Vondra <tomas.vondra@enterprisedb.com>

To: Soumyadeep Chakraborty <soumyadeep2007@gmail.com>, Matthias van de Meent <boekewurm+postgres@gmail.com>

Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, pgsql-hackers <pgsql-hackers@postgresql.org>, Ashwin Agrawal <ashwinstar@gmail.com>

Date: 2023-11-25T20:06:03Z

Lists: pgsql-hackers

I've done a bit more cleanup on the last version of the patch (renamed
the fields to start with bis_ as agreed, rephrased the comments / docs /
commit message a bit) and pushed.

Thanks for the patch!

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

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

Add missing index_insert_cleanup calls
- 41d2c6f952ed 17.0 landed
Fix a couple typos in BRIN code
- 95d14b7ae26d 17.0 landed
Check if ii_AmCache is NULL in aminsertcleanup
- a82ee7ef3aac 17.0 landed
Use fipshash in brin_multi test
- 86b64bafc19c 17.0 cited
Reuse BrinDesc and BrinRevmap in brininsert
- c1ec02be1d79 17.0 landed
Consider fillfactor when estimating relation size
- 29cf61ade3f2 17.0 cited
Postpone some stuff out of ExecInitModifyTable.
- c5b7ba4e67ae 14.0 cited