Ensuring Concurrent Query Safety in Postgres Clusters
I have a question regarding the postgres database in cluster. How is it protecting that not two workflows are at the same time making a query and writing to the same table? I personally like how neon (key-value store with postgres) or cockroachdb (https://neon.tech/blog/get-page-at-lsn) is doing distributed sql computing by scaling the database horizontally and based on changes in the table then functions are triggered. This is scaling also very well as key-value stores can be merged well together and the hash is like the ID in shardcake. How would one do this in cluster?
