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 15:35:26 -0500
Message-ID: <8089.1448656526@sss.pgh.pa.us> (raw)
In-Reply-To: <20151127195328.GE4320@alvherre.pgsql>
References: <62FE8F79-7278-4AE0-9FDE-0C0277A7B609@gmail.com>
<20151127184936.GD4320@alvherre.pgsql>
<5403.1448652828@sss.pgh.pa.us>
<20151127195328.GE4320@alvherre.pgsql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Alvaro Herrera <alvherre@2ndquadrant.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
--
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: <8089.1448656526@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