Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM

From: Jingtang Zhang <mrdrivingduck(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM
Date: 2024-10-29 03:18:42
Message-ID: CAPsk3_AuOsLcOrgTX4-QDP0Qv+AHBuuH3fTK6MwVacH6gvR1Nw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi~

Sorry for multiple comments in separate mail. Just found that the initialization
seems redundant since we have used palloc0?

> + istate = (HeapInsertState *) palloc0(sizeof(HeapInsertState));
> + istate->bistate = NULL;
> + istate->mistate = NULL;

---
Regards, Jingtang

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message cca5507 2024-10-29 03:21:15 Re: Reduce one comparison in binaryheap's sift down
Previous Message David Rowley 2024-10-29 03:06:25 Re: EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on