| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Alexandre Arruda <adaldeia(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ERROR: found multixact from before relminmxid |
| Date: | 2018-04-10 03:08:02 |
| Message-ID: | CAH2-Wzn09Eqt6SV=P=T02m=8kdOCYdV2Y5nSVFQSKzz8tkY8gg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Apr 9, 2018 at 7:53 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I've not followed this thread. Possible it's the overeager check for pg upgraded tuples from before 9.3 that Alvaro fixed recently?
I was aware of commit 477ad05e, which must be what you're referring
to. I don't think that that's what this is, since this error occurs
within heap_freeze_tuple() -- it's not the over-enforced
HEAP_XMAX_IS_LOCKED_ONLY() error within heap_prepare_freeze_tuple().
And, because this database wasn't pg_upgraded.
I should wait until tomorrow before doing any further analysis, though.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hans Schou | 2018-04-10 08:36:28 | Grant to a group defined in Windows AD |
| Previous Message | Andres Freund | 2018-04-10 02:53:23 | Re: ERROR: found multixact from before relminmxid |