Re: Summary and Plan for Hot Standby
От | Simon Riggs |
---|---|
Тема | Re: Summary and Plan for Hot Standby |
Дата | |
Msg-id | 1258621205.27757.976.camel@ebony обсуждение исходный текст |
Ответ на | Re: Summary and Plan for Hot Standby (Tatsuo Ishii <ishii@sraoss.co.jp>) |
Ответы |
Re: Summary and Plan for Hot Standby
|
Список | pgsql-hackers |
On Thu, 2009-11-19 at 17:15 +0900, Tatsuo Ishii wrote: > > Simon Riggs wrote: > > > Recovery does *not* take the same locks as the original statements on > > > the master took. For example, the WAL record for an INSERT just makes > > > its changes without acquiring locks. This is OK as long as we only allow > > > read-only users to acquire AccessShareLocks. If we allowed higher locks > > > we might need to do deadlock detection, which would add more complexity. > > > > But we *do* allow higher locks than AccessShareLocks, as Tatsuo-sans > > example shows. Is that a bug? > > Sorry for confusion. My example is under normal PostgreSQL, not under > HS enabled. Are you saying you want it to work in HS mode? Why would you want to PREPARE an INSERT, but never execute it? -- Simon Riggs www.2ndQuadrant.com
В списке pgsql-hackers по дате отправления: