Re: ERROR could not access transaction/Could not open file pg_commit_ts

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Jeremy Finzel <finzelj(at)gmail(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: ERROR could not access transaction/Could not open file pg_commit_ts
Date: 2018-03-09 18:40:52
Message-ID: 20180309184052.myncevkzh2iivbnt@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jeremy Finzel wrote:

> UPDATE: what is actually failing is a call to
> pg_xact_commit_timestamp(xmin) on a given table under the view. We still
> think we must have some corruption though with pg_commit_ts.

This is not a valid query, because the xmin may belong to a frozen
tuple. pg_commit_ts does not keep data forever; old files are removed.
Anything older than datfrozenxid could return that error.

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Charlin Barak 2018-03-09 20:08:33 how to get list of sequences owned by a user/role
Previous Message Jeremy Finzel 2018-03-09 18:34:04 Re: ERROR could not access transaction/Could not open file pg_commit_ts