Re: SSI non-serializable UPDATE performance
От | Simon Riggs |
---|---|
Тема | Re: SSI non-serializable UPDATE performance |
Дата | |
Msg-id | BANLkTi=DVO4MV1pa8==e2ka1Bgwg-vN+qw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: SSI non-serializable UPDATE performance (Dan Ports <drkp@csail.mit.edu>) |
Ответы |
Re: SSI non-serializable UPDATE performance
Re: SSI non-serializable UPDATE performance |
Список | pgsql-hackers |
On Mon, Apr 25, 2011 at 4:33 AM, Dan Ports <drkp@csail.mit.edu> wrote: > On Sat, Apr 23, 2011 at 08:54:31AM -0500, Kevin Grittner wrote: >> Even though this didn't show any difference in Dan's performance >> tests, it seems like reasonable insurance against creating a new >> bottleneck in very high concurrency situations. >> >> Dan, do you have a patch for this, or should I create one? > > Sure, patch is attached. Reading the code, IIUC, we check for RW conflicts after each write but only if the writer is running a serializable transaction. Am I correct in thinking that there is zero impact of SSI if nobody is running a serializable transaction? -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: