Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
От | Andres Freund |
---|---|
Тема | Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts |
Дата | |
Msg-id | 20140721170953.GP5974@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
|
Список | pgsql-bugs |
On 2014-07-21 13:03:21 -0400, Tom Lane wrote: > Andres Freund <andres@2ndquadrant.com> writes: > > On 2014-07-21 12:43:24 -0400, Tom Lane wrote: > >> Will fix. > > > I wonder if GetTopTransactionId()/MultiXactIdSetOldestMember() and using > > lastSane* = ReadNew* isn't sufficient. After the xid assignment > > concurrent GetOldest* can't go below the ReadNew* values anymore, right? > > I don't see any point in being picky about it. What we want is to reject > values that are conclusively bogus; things that are just close to bogus > are not so interesting. It'd just have been about optimizing away repeated calls to ReadNew*... Thanks. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-bugs по дате отправления: