3 ms·
> Table Changes Without Locking > MyIsam uses table-locking to gain speed. That’s fine if many sessions involve reading; but when writing to a table, the writin
by takeda 12y ago
> Table Changes Without Locking
> MyIsam uses table-locking to gain speed. That’s fine if many sessions involve reading; but when writing to a table, the writing session gets exclusive access and other sessions must wait until its finished. But PostgreSQl and InnoDB both use row-level locking…so again, it’s much less of an issue.
I am not sure I can agree with this one as well, but at least postgres does normally not use row level locking anymore (in 10 years?) because of MVCC.
- AlisdairO 12y agoPostgres does use row level locking, it just doesn't lock for reads - so you still get write-write conflicts on the same row. The same is true for InnoDB.