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

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Kouber Saparev wrote:
>> Recently I spotted an auto vacuum that is constantly being run over a pg_toast table in the database. Interestingly the underlying table did not have that amount of writes that would trigger the auto vacuum every minute.
>>
>> When I tried to run the VACUUM manually it died with a non-existent MultiXactId error:
>>
>> db=# vacuum analyze verbose pg_toast.pg_toast_376621;
>> INFO: vacuuming "pg_toast.pg_toast_376621"
>> ERROR: MultiXactId 2915905228 does no longer exist -- apparent wraparound

> Hmm, I don't think there can be multixacts in toast tables at all,
> normally.

Couldn't creation and deletion of a toasted object within the same
transaction do it?

regards, tom lane