From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Kouber Saparev <kouber@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: VACUUM unable to accomplish because of a non-existent MultiXactId
Date: Fri, 27 Nov 2015 14:33:48 -0500
Message-ID: <5403.1448652828@sss.pgh.pa.us> (raw)
In-Reply-To: <20151127184936.GD4320@alvherre.pgsql>
References: <62FE8F79-7278-4AE0-9FDE-0C0277A7B609@gmail.com>
<20151127184936.GD4320@alvherre.pgsql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, kouber@gmail.com
Subject: Re: VACUUM unable to accomplish because of a non-existent MultiXactId
In-Reply-To: <5403.1448652828@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox