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

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: laurenz(dot)albe(at)cybertec(dot)at, 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-29 17:29:15
Message-ID: 202311291729.d375fgxfxmlp@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

On 2023-Nov-28, Kyotaro Horiguchi wrote:

> 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?

If the file is exactly of the length given then seek will work, and read
will not set errno but return a length of 0 bytes. So
SlruPhysicalReadPage sets SLRU_READ_FAILED and then in pg11 the %m in
SlruReportIOError expands to "Success".

The code in master is completely different (it uses pg_pread rather than
seek + read): it does test for errno and reports accordingly.

So, nothing to do here.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ron Johnson 2023-11-29 20:24:51 Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
Previous Message Sri Mrudula Attili 2023-11-29 17:20:20 Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2023-11-29 20:24:51 Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
Previous Message Sri Mrudula Attili 2023-11-29 17:20:20 Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.