Re: [HACKERS] CurTransactionContext freed before transaction COMMIT ???

Thanks for your responses Michael and Amit Kapila, Yes, we have included your suggestions in our code and started testing to reproduce the same issue. In case we encounter this issue again we will get back here. Regards G. Sai Ram

Re: [HACKERS] CurTransactionContext freed before transaction COMMIT ???

On Wed, Oct 25, 2017 at 8:04 PM, Gaddam Sai Ram wrote: > 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

Re: [HACKERS] CurTransactionContext freed before transaction COMMIT ???

On Wed, Oct 25, 2017 at 7:34 AM, Gaddam Sai Ram wrote: > 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?

Re: [HACKERS] CurTransactionContext freed before transaction COMMIT ???

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

Re: [HACKERS] CurTransactionContext freed before transaction COMMIT ???

On Tue, Oct 24, 2017 at 7:42 PM, Gaddam Sai Ram wrote: > > Hello people, > > We are implementing in-memory index. As a part of that, during > index callbacks, under CurTransactionContext, we cache all the DMLs of a > transaction in dlist(postgres's

Re: [HACKERS] CurTransactionContext freed before transaction COMMIT ???

This sounds broken on its face --- if you want stuff to survive to top-level commit, you need to keep it in TopTransactionContext. CurTransactionContext might be a subtransaction's context that will go away at subtransaction commit/abort.

Re: [HACKERS] CurTransactionContext freed before transaction COMMIT ???

Gaddam Sai Ram writes: > We are implementing in-memory index. As a part of that, during > index callbacks, under CurTransactionContext, we cache all the DMLs of a > transaction in dlist(postgres's doubly linked list). > We registered

[HACKERS] CurTransactionContext freed before transaction COMMIT ???

Hello people, We are implementing in-memory index. As a part of that, during index callbacks, under CurTransactionContext, we cache all the DMLs of a transaction in dlist(postgres's doubly linked list). We registered transaction callback, and in transaction