Re: Read only transactions - Commit or Rollback
| От | Markus Schaber |
|---|---|
| Тема | Re: Read only transactions - Commit or Rollback |
| Дата | |
| Msg-id | 43A7F9B9.3010906@logix-tt.com обсуждение исходный текст |
| Ответ на | Re: Read only transactions - Commit or Rollback (Andreas Seltenreich <andreas+pg@gate450.dyndns.org>) |
| Ответы |
Re: Read only transactions - Commit or Rollback
|
| Список | pgsql-performance |
Hello, Andreas, Andreas Seltenreich wrote: >>Btw, there's another setting that might make a difference: >>Having ACID-Level SERIALIZABLE or READ COMMITED? > > Well, if nonrepeatable or phantom reads would pose a problem because > of those occasional writes, you wouldn't be considering autocommit for > performance reasons either, would you? Yes, the question is purely performance-wise. We don't care about any read/write conflicts in this special case. Some time ago, I had some tests with large bulk insertions, and it turned out that SERIALIZABLE seemed to be 30% faster, which surprised us. That's why I ask this questions, and mainly because we currently cannot perform a large bunch of benchmarking. Thanks, Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
В списке pgsql-performance по дате отправления: