Re: Parallel scan with SubTransGetTopmostTransaction assert coredump - Mailing list pgsql-hackers

From Maxim Orlov
Subject Re: Parallel scan with SubTransGetTopmostTransaction assert coredump
Date
Msg-id 08ae178b309c617a9701cbc7ed8a98f0@postgrespro.ru
Whole thread Raw
In response to Re: Parallel scan with SubTransGetTopmostTransaction assert coredump  (Maxim Orlov <m.orlov@postgrespro.ru>)
Responses Re: Parallel scan with SubTransGetTopmostTransaction assert coredump  (Greg Nancarrow <gregn4422@gmail.com>)
List pgsql-hackers
The analysis in the beginning of the discussion seems to be right, but 
the fix v2 looks too invasive for me.

Personally, I'd like not to remove snapshot even if transaction is 
read-only. I propose to consider "xid < TransactionXmin" as a legit case 
and just promote xid to TransactionXmin.

It's annoying this old bug still not fixed. What do you think?
---
Best regards,
Maxim Orlov.
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Maintaining a list of pgindent commits for "git blame" to ignore
Next
From: Peter Geoghegan
Date:
Subject: Re: Maintaining a list of pgindent commits for "git blame" to ignore