Re: Hot Standby dev build (v8)
От | Simon Riggs |
---|---|
Тема | Re: Hot Standby dev build (v8) |
Дата | |
Msg-id | 1232140505.31669.102.camel@ebony.2ndQuadrant обсуждение исходный текст |
Ответ на | Re: Hot Standby dev build (v8) (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: Hot Standby dev build (v8)
|
Список | pgsql-hackers |
On Fri, 2009-01-16 at 22:09 +0200, Heikki Linnakangas wrote: > >> RecentGlobalXmin is just a hint, it lags behind the real oldest xmin > >> that GetOldestXmin() would return. If another backend has a more recent > >> RecentGlobalXmin value, and has killed more recent tuples on the page, > >> the latestRemovedXid written here is too old. > > > > What do you think we should do instead? > > Dunno. Maybe call GetOldestXmin(). We are discussing btree deletes, not btree vacuums. If we are doing btree delete then we have an unreleased snapshot therefore we also have a non-zero xmin. How can another backend have a later RecentGlobalXmin or result from GetOldestXmin() than we do? -- Simon Riggs www.2ndQuadrant.comPostgreSQL Training, Services and Support
В списке pgsql-hackers по дате отправления: