Re: Could not open file pg_xact/0E97

From: Radoslav Nedyalkov <rnedyalkov(at)gmail(dot)com>
To: Jeremy Schneider <schneider(at)ardentperf(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Could not open file pg_xact/0E97
Date: 2020-07-21 07:24:38
Message-ID: CANhtRiaSow71YKPObH_YAnx7Vn6+p__SjB_a2d8aQV9nAfWGjg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Nope. It's an intensive OLAP data-warehouse with queries hanging in waits
for hours.
From the vacuum full error and commit file which is gone due to the
supposedly moved age mark,
It looks more like a bug and not an IO error.

Rado

On Tue, Jul 21, 2020 at 2:38 AM Jeremy Schneider <schneider(at)ardentperf(dot)com>
wrote:

>
> On Jul 18, 2020, at 14:18, Radoslav Nedyalkov <rnedyalkov(at)gmail(dot)com>
> wrote:
>
> 
> Well. the vacuum full failed with
>
> vacuumdb: vacuuming of table "olap.transactions_and_fees_2020_01" in
> database "db" failed: ERROR: found xmin 3916900817 from before
> relfrozenxid 80319533
>
>>
> Do you have checksums enabled for this database?
>
> -Jeremy
>
> Sent from my TI-83
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vasu Madhineni 2020-07-21 07:35:54 Re: Multitenent architecture
Previous Message Thomas Kellerer 2020-07-21 05:48:03 Re: Logical replication from 11.x to 12.x and "unique key violations"