| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts |
| Date: | 2014-07-21 17:09:53 |
| Message-ID: | 20140721170953.GP5974@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2014-07-21 13:03:21 -0400, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-07-21 17:17:25 | Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts |
| Previous Message | Tom Lane | 2014-07-21 17:03:21 | Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts |