Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
Date
Msg-id 3766597.1678146140@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-bugs
Tree view 
Thomas Munro <thomas.munro@gmail.com> writes:
> As mentioned, this approach allows for more improvements in later
> patches.  There is absolutely no reason for transactions in separate
> databases to be in each others' possibleUnsafeConflicts lists.

What if they both touched/modified a shared catalog?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction
Next
From: Thomas Munro
Date:
Subject: Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction