Re: User-facing aspects of serializable transactions
От | Greg Stark |
---|---|
Тема | Re: User-facing aspects of serializable transactions |
Дата | |
Msg-id | 4136ffa0906011157td9dc46bvf8cdb7518a386d42@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: User-facing aspects of serializable transactions (Josh Berkus <josh@agliodbs.com>) |
Список | pgsql-hackers |
On Mon, Jun 1, 2009 at 7:24 PM, Josh Berkus <josh@agliodbs.com> wrote: >> Since some (like MS SQL Server) allow users to choose >> snapshot isolation or blocking-based serializable transactions in >> their MVCC implementation > > This approach allowed MSSQL to "clean up" on TPCE; to date their performance > on that benchmark is so much better than anyone else nobody else wants to > publish. Are you sure you aren't thinking of some other feature? An implementation of Serializable transactions isn't going to suddenly make MSSQL faster than Oracle which uses snapshots anyways. From what I remember TPC-E actually spends most of its energy testing things like check constraints, referential integrity checks, and complex queries. What you describe is possible but it's seems more likely to be due to some kind of optimization like materialized views or cached query results or something like that. -- greg
В списке pgsql-hackers по дате отправления: