snazy opened a new issue, #777: URL: https://github.com/apache/polaris/issues/777
### Describe the bug As pointed out on the [mailing list](https://lists.apache.org/thread/obvrrh0w36f87rwljptzwonpt89qkcm1), the current persistence implementation in Polaris, even if run with the required isolation level, yields errors like `ERROR: could not serialize access due to read/write dependencies among transactions`. The underlying test case, which runs concurrent modifications to _different_ Iceberg tables (non-conflicting changes) and did not "overload" Polaris, should really _never_ yield such errors to users. This issue _could_ be a consequence of #775, assuming that the behavior of one persistence backend can be ported 1:1 to another one. ### To Reproduce _No response_ ### Actual Behavior _No response_ ### Expected Behavior _No response_ ### Additional context _No response_ ### System information _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
