On 2018-May-31, PG Bug reporting form wrote:
> we're using postgresql 10.2, postgresql is deployed in a docker image. it
> works well for some time. but one day we met errors when we test with load.
> In logs, we found below errors:
>
> 2018-05-28T10:08:38.487336192Z 2018-05-28 10:08:38.487 UTC [110] ERROR:
> could not access status of transaction 0
> 2018-05-28T10:08:38.487348231Z 2018-05-28 10:08:38.487 UTC [110] DETAIL:
> Could not open file "pg_subtrans/0013": Invalid argument.
While reviewing this bug report a few days ago I noticed that there was
one place that would report "could not open file" on a failure to
lseek(), because a wrong enum value used as function indicator was set.
It could not possibly be involved in this report, because that code is
only used by multixact.c and commit_ts.c in branch 10. Nevertheless, I
applied a patch to fix that.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
