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

From Amit Kapila
Subject Re: Decoding speculative insert with toast leaks memory
Date
Msg-id CAA4eK1Kmj9HzdDPOW3HFaq0A0=d7Ng_qyH3T=7yk0=MYcPZ6Qg@mail.gmail.com
Whole thread Raw
In response to Re: Decoding speculative insert with toast leaks memory  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Responses Re: Decoding speculative insert with toast leaks memory
List pgsql-hackers
On Fri, May 28, 2021 at 5:16 PM Tomas Vondra
<tomas.vondra@enterprisedb.com> wrote:
>
> I wonder if there's a way to free the TOASTed data earlier, instead of
> waiting until the end of the transaction (as this patch does).
>

IIUC we are anyway freeing the toasted data at the next
insert/update/delete. We can try to free at other change message types
like REORDER_BUFFER_CHANGE_MESSAGE but as you said that may make the
patch more complex, so it seems better to do the fix on the lines of
what is proposed in the patch.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Parallel Inserts in CREATE TABLE AS
Next
From: Amit Kapila
Date:
Subject: Re: Skipping logical replication transactions on subscriber side