pgsql: Fix decoding of speculative aborts.

2021-06-14 Thread Amit Kapila
Fix decoding of speculative aborts. During decoding for speculative inserts, we were relying for cleaning toast hash on confirmation records or next change records. But that could lead to multiple problems (a) memory leak if there is neither a confirmation record nor any other record after toast i

pgsql: Fix decoding of speculative aborts.

2021-06-14 Thread Amit Kapila
Fix decoding of speculative aborts. During decoding for speculative inserts, we were relying for cleaning toast hash on confirmation records or next change records. But that could lead to multiple problems (a) memory leak if there is neither a confirmation record nor any other record after toast i

pgsql: Fix decoding of speculative aborts.

2021-06-14 Thread Amit Kapila
Fix decoding of speculative aborts. During decoding for speculative inserts, we were relying for cleaning toast hash on confirmation records or next change records. But that could lead to multiple problems (a) memory leak if there is neither a confirmation record nor any other record after toast i

pgsql: Fix decoding of speculative aborts.

2021-06-14 Thread Amit Kapila
Fix decoding of speculative aborts. During decoding for speculative inserts, we were relying for cleaning toast hash on confirmation records or next change records. But that could lead to multiple problems (a) memory leak if there is neither a confirmation record nor any other record after toast i

pgsql: Fix decoding of speculative aborts.

2021-06-14 Thread Amit Kapila
Fix decoding of speculative aborts. During decoding for speculative inserts, we were relying for cleaning toast hash on confirmation records or next change records. But that could lead to multiple problems (a) memory leak if there is neither a confirmation record nor any other record after toast i

pgsql: Fix decoding of speculative aborts.

2021-06-14 Thread Amit Kapila
Fix decoding of speculative aborts. During decoding for speculative inserts, we were relying for cleaning toast hash on confirmation records or next change records. But that could lead to multiple problems (a) memory leak if there is neither a confirmation record nor any other record after toast i