"Kenneth Downs" <[EMAIL PROTECTED]> writes: > RPK wrote: >> I want to know whether MVCC has cons also. Is it heavy on resources? How >> PGSQL MVCC relates with SQL Server 2005 new Snapshot Isolation.
Well the fundamental con of MVCC versus serializing everything using locks is that you have to keep more data around which takes space and i/o resources. > Speaking as an end-user, I can give only one I've ever seen, which is > performance. Because of MVCC, Postgres's write performance (insert and > update) > appears on my systems to be almost exactly linear to row size. Inserting 1000 > rows into a table with row size 100 characters takes twice as long as > inserting > 1000 rows into a table with row size 50 characters. Well, that's going to be true (assuming i/o is your limiting factor at all) regardless of your architecture. There's no magic here, more bytes take more blocks of space which take more time to write or read. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org/
