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
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 to CurTransactionContext, can y
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?
Assert(MemoryContextIsValid(CurTransactionContext));
--
Michael
--
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
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 doubly linked list).
> W
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.
https://github.com/postgres/postgres/blob/
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 transaction callback, and in transacti
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 pre-commi