Re: Decoding speculative insert with toast leaks memory

Alvaro Herrera <alvherre@alvh.no-ip.org>

From: Alvaro Herrera <alvherre@alvh.no-ip.org>

To: Dilip Kumar <dilipbalaut@gmail.com>

Cc: Amit Kapila <amit.kapila16@gmail.com>, Andres Freund <andres@anarazel.de>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Petr Jelinek <petr.jelinek@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Tomas Vondra <tomas.vondra@enterprisedb.com>

Date: 2021-06-09T15:29:17Z

Lists: pgsql-hackers

May I suggest to use a different name in the blurt_and_lock_123()
function, so that it doesn't conflict with the one in
insert-conflict-specconflict?  Thanks

-- 
Álvaro Herrera                            39°49'30"S 73°17'W

Commits

Fix ABI break introduced by commit 4daa140a2f.
- e95f617acc48 11.13 landed
- 72b51e214a2c 12.8 landed
- 56e366f6757d 13.4 landed
Fix valgrind issue in pgoutput.c.
- 357cb8f07f95 13.4 landed
Fix decoding of speculative aborts.
- 43acadfcebec 9.6.23 landed
- 35f56c124a7a 10.18 landed
- 1f8a934e0a86 11.13 landed
- 40ad7ebff6ca 12.8 landed
- 602a32a685e4 13.4 landed
- 4daa140a2f50 14.0 landed
pgoutput: Fix memory leak due to RelationSyncEntry.map.
- d2505681211b 13.4 cited
Fix initialization of RelationSyncEntry for streaming transactions.
- 69bd60672af6 14.0 cited
Implement streaming mode in ReorderBuffer.
- 7259736a6e5b 14.0 cited