Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] CurTransactionContext freed before transaction COMMIT??? - Mailing list pgsql-hackers

From Gaddam Sai Ram
Subject Re: [HACKERS] CurTransactionContext freed before transaction COMMIT???
Date
Msg-id 15f53f4c47f.11498d9f3777.5163761064174298129@zohocorp.com
Whole thread Raw
In response to Re: [HACKERS] CurTransactionContext freed before transaction COMMIT ???  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [HACKERS] CurTransactionContext freed before transaction COMMIT ???
Re: [HACKERS] CurTransactionContext freed before transaction COMMIT ???
List pgsql-hackers
Tree view
Thanks for the response,

Can you check if CurTransactionContext is valid at that point? 

Any Postgres function to check if CurTransactionContext is valid or not?

To see, if this problem is related to CurTransactionContext, can you try to populate the list in TopMemoryContext and see if that works.

Did you mean TopTransactionContext? 
As of now, we don't free our dlist. We solely depend on Postgres to free our dlist while it frees the TopTransactionContext. But if we do allocate in TopMemoryContext, we need to take care of freeing our allocations.

And one more issue is, we found this bug once in all the testing we did. So trying to replay this bug seems very difficult.

Regards,
G. Sai Ram

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] CurTransactionContext freed before transaction COMMIT ???
Next
From: Michael Paquier
Date:
Subject: [HACKERS] Re: [BUGS] BUG #14849: jsonb_build_object doesn't like VARIADIC callsvery much