[Postgres-xl-bugs] could not read block 0 in file "base/22958/1042884"

Shaun Thomas sthomas at peak6.com
Thu Jun 9 11:48:10 PDT 2016


> I looked at the code a bit, but this doesn't seem like a simple fix. I
> would rather block FOR UPDATE, at least for queries that can't
> guarantee proper and accurate locking of the rows.

Interesting. Perhaps blocking FOR UPDATE would make sense in the case of a JOIN, which is what seems to be causing the actual problem. Without the JOIN, there's no potential for a node mismatch. To me, that would be similar to how Postgres restricts view updates.

Beyond that though, this makes me wonder what other inter-node conflicts are lurking in the system.

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email


More information about the postgres-xl-bugs mailing list