pgbench: Remove now-dead CState->ecnt
The last use of ecnt was in 12788ae. It was getting incremented after a
backend error without any purpose since then, so let's get rid of it.
Author: Kota Miyake
Reviewed-by: Álvaro Herrera
Discussion: https://postgr.es/m/786c3d9fbe067763d899e78c296f9...@oss
Fix use-after-free bug with AfterTriggersTableData.storeslot
AfterTriggerSaveEvent() wrongly allocates the slot in execution-span
memory context, whereas the correct thing is to allocate it in
a transaction-span context, because that's where the enclosing
AfterTriggersTableData instance belongs in
Fix use-after-free bug with AfterTriggersTableData.storeslot
AfterTriggerSaveEvent() wrongly allocates the slot in execution-span
memory context, whereas the correct thing is to allocate it in
a transaction-span context, because that's where the enclosing
AfterTriggersTableData instance belongs in
Fix use-after-free bug with AfterTriggersTableData.storeslot
AfterTriggerSaveEvent() wrongly allocates the slot in execution-span
memory context, whereas the correct thing is to allocate it in
a transaction-span context, because that's where the enclosing
AfterTriggersTableData instance belongs in
Fix use-after-free bug with AfterTriggersTableData.storeslot
AfterTriggerSaveEvent() wrongly allocates the slot in execution-span
memory context, whereas the correct thing is to allocate it in
a transaction-span context, because that's where the enclosing
AfterTriggersTableData instance belongs in
Raise a timeout to 180s, in contrib/test_decoding.
Per buildfarm member hornet. The test is new in v14, so no back-patch.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/388b959315205b0b65efb074ec84e1d7fad62402
Modified Files
--
contrib/test_decoding/e
Add missing TidRangeScan readfunc
Mistakenly forgotten in bb437f995
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/977b2c08535f2a82ba7c310c88420cbbca1772e8
Modified Files
--
src/backend/nodes/readfuncs.c | 17 +
1 file changed, 17 insert
Add TID Range Scans to support efficient scanning ranges of TIDs
This adds a new executor node named TID Range Scan. The query planner
will generate paths for TID Range scans when quals are discovered on base
relations which search for ranges on the table's ctid column. These
ranges may be open