Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: laurenz(dot)albe(at)cybertec(dot)at
Cc: sri(at)ebi(dot)ac(dot)uk, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
Date: 2023-11-28 08:54:43
Message-ID: 20231128.175443.1171037512392479311.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

At Mon, 27 Nov 2023 19:58:13 +0100, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote in
> On Mon, 2023-11-27 at 11:50 +0000, Sri Mrudula Attili wrote:
> > ERROR:  could not access status of transaction 16087052
> > DETAIL:  Could not read from file "pg_subtrans/00F5" at offset 122880: Success.

By the way, just out of curiosity, but errno should not be zero at the
time the message above was output, yet "%m" is showing "success",
which implies errno = 0 in Linux. How can that happen?

slru.c:961
> case SLRU_READ_FAILED:
> if (errno)
> ereport(ERROR,
> (errcode_for_file_access(),
> errmsg("could not access status of transaction %u", xid),
> errdetail("Could not read from file \"%s\" at offset %d: %m.",

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Lakhin 2023-11-28 09:00:00 Re: BUG #17893: Assert failed in heap_update()/_delete() when FK modiified by RI trigger in non-read-committed xact
Previous Message Andrei Lepikhov 2023-11-28 08:24:51 Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN

Browse pgsql-general by date

  From Date Subject
Next Message Dominique Devienne 2023-11-28 12:12:20 Get back the number of columns of a result-set prior to JSON aggregation
Previous Message Filip Sedlák 2023-11-28 07:36:32 Re: Emitting JSON to file using COPY TO