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
wrote:
>
> On
> On Jul 18, 2020, at 14:18, Radoslav Nedyalkov 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
see
> pg_dump: Dumping the contents of table "transactions_and_fees_2020_01"
> failed: PQgetResult() failed.
> pg_dump: Error message from server: ERROR: could not access status of
> transaction 3916900817
> DETAIL: Could not open file "pg_xact/0E97": No such
Hi Forum,
We see
pg_dump: Dumping the contents of table "transactions_and_fees_2020_01"
failed: PQgetResult() failed.
pg_dump: Error message from server: ERROR: could not access status of
transaction 3916900817
DETAIL: Could not open file "pg_xact/0E97": No such file or d
