agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: jim_yates <pg@wg5jim.net>
To: pgsql-sql@postgresql.org
Subject: Re: could not access status of transaction pg_multixact issue
Date: Thu, 9 Oct 2014 14:51:05 -0700 (PDT)
Message-ID: <1412891465175-5822482.post@n5.nabble.com> (raw)
In-Reply-To: <20141009203637.GH7043@eldon.alvh.no-ip.org>
References: <20141008185538.GY7043@eldon.alvh.no-ip.org>
<1412797415000-5822268.post@n5.nabble.com>
<20141008205416.GZ7043@eldon.alvh.no-ip.org>
<1412863620263-5822376.post@n5.nabble.com>
<5436A34C.8090306@aklaver.com>
<20141009151229.GD7043@eldon.alvh.no-ip.org>
<1412874160409-5822399.post@n5.nabble.com>
<20141009180022.GE7043@eldon.alvh.no-ip.org>
<1412885826355-5822449.post@n5.nabble.com>
<20141009203637.GH7043@eldon.alvh.no-ip.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
Alvaro Herrera-9 wrote
> I'm deep in another issue which I don't want to page out right now, but
> try vacuuming the tables that have relminmxid=1 with low values set for
> vacuum_multixact_freeze_table_age and vacuum_multixact_freeze_min_age,
> say 100000. (I think 65536 ought to get you beyond segment
> pg_multixact/offset/0000, and then that file would be removed.) Since
> any multixact values below the point at which pg_upgrade ran should be
> marked "no longer running" through hint bits, there would be no
> pg_multixact lookups anyway and thus the vacuuming should complete with
> no errors.
>
> --
> Álvaro Herrera http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
No joy:
acustream=# set vacuum_multixact_freeze_table_age=100000;
SET
acustream=# set vacuum_multixact_freeze_min_age=100000;
SET
acustream=# vacuum phyorg_charges_to_invoice;
ERROR: could not access status of transaction 182579
DETAIL: Could not open file "pg_multixact/members/EEAC": No such file or
directory.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/could-not-access-status-of-transaction-pg-multixact-issue-tp...
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
view thread (16+ messages) latest in thread
Message-ID: <1412891465175-5822482.post@n5.nabble.com>
Permalink: ../1412891465175-5822482.post@n5.nabble.com/
Also on: postgresql.org/message-id/1412891465175-5822482.post@n5.nabble.com
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-sql@postgresql.org
Cc: pg@wg5jim.net
Subject: Re: could not access status of transaction pg_multixact issue
In-Reply-To: <1412891465175-5822482.post@n5.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox