Re: VACUUM unable to accomplish because of a non-existent MultiXactId

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Kouber Saparev <kouber(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: VACUUM unable to accomplish because of a non-existent MultiXactId
Date: 2015-11-27 20:35:26
Message-ID: 8089.1448656526@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Tom Lane wrote:
>> Couldn't creation and deletion of a toasted object within the same
>> transaction do it?

> I tried and couldn't find a way to cause one to appear. When a row is
> created, it has xmax=0 so when it's deleted the xmax can just be set to
> the deleting xact. And we don't ever update pg_toast rows, AFAIK.

Ah, nevermind, brain fade ... I was momentarily confusing this with
combo CIDs. Right, there are no updates or row locks taken on toast
table rows (unless someone were to do one manually?)

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alvaro Herrera 2015-11-27 20:47:57 Re: VACUUM unable to accomplish because of a non-existent MultiXactId
Previous Message Alvaro Herrera 2015-11-27 19:53:28 Re: VACUUM unable to accomplish because of a non-existent MultiXactId