Postgres Pro
Downloads
Home   >   mailing lists

Re: Decoding speculative insert with toast leaks memory - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Decoding speculative insert with toast leaks memory
Date
Msg-id CAFiTN-vHmMm=Mq8VBhOO5NgKe1As914rdo0uMNxQrwELkHRFPw@mail.gmail.com
Whole thread Raw
In response to Re: Decoding speculative insert with toast leaks memory  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Decoding speculative insert with toast leaks memory
List pgsql-hackers
Tree view 
On Thu, May 27, 2021 at 9:47 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Thu, May 27, 2021 at 9:40 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> True, but if you do this clean-up in ReorderBufferCleanupTXN then you
> don't need to take care at separate places. Also, toast_hash is stored
> in txn so it appears natural to clean it up in while releasing TXN.

Make sense, basically, IMHO we will have to do in TruncateTXN and
ReturnTXN as attached?

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
Attachment

pgsql-hackers by date:

Previous
From: Andrey Lepikhov
Date:
Subject: Re: Asymmetric partition-wise JOIN
Next
From: Bharath Rupireddy
Date:
Subject: Re: Parallel Inserts in CREATE TABLE AS