| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: MultiXactId error after upgrade to 9.3.4 |
| Date: | 2016-06-17 22:55:17 |
| Message-ID: | 20160617225517.GA157662@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Andrew Gierth wrote:
> > Why is the correct rule not "check for and ignore pre-upgrade mxids
> > before even trying to fetch members"?
>
> I propose something like the attached patch, which implements that idea.
Here's a backpatch of that to 9.3 and 9.4.
I tested this by creating a 9.2 installation with an out-of-range
multixact, and verified that after upgrading this to 9.3 it fails with
the "apparent wraparound" message in VACUUM. With this patch applied,
it silently removes the multixact.
I will clean this up and push to all branches after the tagging of
9.6beta2 on Monday.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| upgraded-locks-93.patch | text/x-diff | 10.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-06-18 00:41:54 | Re: pgsql: Try again to fix the way the scanjoin_target is used with partia |
| Previous Message | Aleksey Demakov | 2016-06-17 22:55:07 | Re: Experimental dynamic memory allocation of postgresql shared memory |