From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
cc: Kouber Saparev <kouber@gmail.com>, pgsql-admin@postgresql.org
Subject: Re: VACUUM unable to accomplish because of a non-existent MultiXactId
In-reply-to: <20151127184936.GD4320@alvherre.pgsql>
References: <62FE8F79-7278-4AE0-9FDE-0C0277A7B609@gmail.com>
 <20151127184936.GD4320@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@2ndquadrant.com>
 message dated "Fri, 27 Nov 2015 15:49:36 -0300"
Date: Fri, 27 Nov 2015 14:33:48 -0500
Message-ID: <5403.1448652828@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Alvaro Herrera <alvherre@2ndquadrant.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


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin