3 ms·

ruh-roh, master-master replication, multithreaded eexecution, vacuuming tables, in-memory OLTP. Yes postgres is cutting edge and without blame. Stay away from t

by blahi 10y ago

ruh-roh, master-master replication, multithreaded eexecution, vacuuming tables, in-memory OLTP. Yes postgres is cutting edge and without blame. Stay away from the evil SQL Server, nothing to be gained there.

serguzest 10y ago
What about true MVCC?
- deleted 10y ago
  [deleted]
- UK-AL 10y ago
  READ_COMMITTED_SNAPSHOT?
  - serguzest 10y ago
    It uses tempdb for tracking versions, it is not mvcc in the core https://news.ycombinator.com/item?id=12693127 https://news.ycombinator.com/item?id=12693127
    - UK-AL 10y ago
      Just because it does it in tempdb, doesn't mean its not MVCC. That's an implementation detail.
      - serguzest 10y ago
        In postgres (and probably in others aswell), MVCC implemented in Btree storage level. there is an overhead to write tempdb.
        anarazel 10y ago
        Btrees in postgres have no visibility information, MVCC is implemented on the heap level.
UK-AL 10y ago
Most of those SQL server can do. There isn't really a need for VACUUM on SQL sever.