Postgres Pro
Downloads
Home   >   mailing lists

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

From Alvaro Herrera
Subject Re: Decoding speculative insert with toast leaks memory
Date
Msg-id 202106091529.d24gsfbiaeut@alvherre.pgsql
Whole thread Raw
In response to Re: Decoding speculative insert with toast leaks memory  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: Decoding speculative insert with toast leaks memory  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers
Tree view 
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

-- 
Álvaro Herrera                            39°49'30"S 73°17'W

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Refactor "mutually exclusive options" error reporting code in parse_subscription_options
Next
From: "Finnerty, Jim"
Date:
Subject: Character expansion with ICU collations