pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
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 17:47:57 -0300
Message-ID: <20151127204757.GF4320@alvherre.pgsql> (raw)
In-Reply-To: <8089.1448656526@sss.pgh.pa.us>
References: <62FE8F79-7278-4AE0-9FDE-0C0277A7B609@gmail.com>
	<20151127184936.GD4320@alvherre.pgsql>
	<5403.1448652828@sss.pgh.pa.us>
	<20151127195328.GE4320@alvherre.pgsql>
	<8089.1448656526@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Tom Lane wrote:
> 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?)

Both UPDATE and SELECT FOR UPDATE fail right away:

alvherre=# update pg_toast.pg_toast_16398 set chunk_id = 7 where chunk_id = 5;
ERROR:  cannot change TOAST relation "pg_toast_16398"

alvherre=# select * from pg_toast.pg_toast_16398 for update;
ERROR:  cannot lock rows in TOAST relation "pg_toast_16398"

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


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



view thread (8+ messages)  latest in thread

Message-ID: <20151127204757.GF4320@alvherre.pgsql>
Permalink:  ../20151127204757.GF4320@alvherre.pgsql/
Also on:    postgresql.org/message-id/20151127204757.GF4320@alvherre.pgsql

 · 

reply

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: alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, kouber@gmail.com
  Subject: Re: VACUUM unable to accomplish because of a non-existent MultiXactId
  In-Reply-To: <20151127204757.GF4320@alvherre.pgsql>

* 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