Does Neon guarantees row level locks to be exclusive? #4226
-
Hello Neon team, I'm reading and trying to understand Neon architecture: https://neon.tech/docs/introduction/architecture-overview According to my understanding (please correct me if I'm wrong), each of the Compute pods are running Postgres server. What happens when there are two row-level lock queries in two different transaction?
Thanks, Rick |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
There is some misunderstanding. Yes, each compute = Postgres instance is running in separate Pod or VM. |
Beta Was this translation helpful? Give feedback.
-
Neon is a single-writer system, there can be only one writer compute pod at a time. Just like in a vanilla Postgres setup with replication. You can have read-only replicas, but you cannot run "SELECT FOR UPDATE" in a read-only node. Transaction handling and MVCC in Neon work the same as in any Postgres installation. |
Beta Was this translation helpful? Give feedback.
Neon is a single-writer system, there can be only one writer compute pod at a time. Just like in a vanilla Postgres setup with replication. You can have read-only replicas, but you cannot run "SELECT FOR UPDATE" in a read-only node. Transaction handling and MVCC in Neon work the same as in any Postgres installation.