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-s3CBwexFVR9=hF4dypxK27YQCTYVfsDj8ZC5OF=ah8WA@mail.gmail.com
Whole thread Raw
In response to Re: Decoding speculative insert with toast leaks memory  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: Decoding speculative insert with toast leaks memory
List pgsql-hackers
Tree view 
On Wed, Jun 9, 2021 at 8:59 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> May I suggest to use a different name in the blurt_and_lock_123()
> function, so that it doesn't conflict with the one in
> insert-conflict-specconflict?  Thanks

Renamed to blurt_and_lock(), is that fine?

I haved fixed other comments and also prepared patches for the back branches.

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

pgsql-hackers by date:

Previous
From: Ajin Cherian
Date:
Subject: Re: Decoding of two-phase xacts missing from CREATE_REPLICATION_SLOT command
Next
From: Peter Eisentraut
Date:
Subject: Re: CALL versus procedures with output-only arguments