From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | joanaliang_05(at)126(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15221: Could not open file "pg_subtrans/0013" |
Date: | 2018-06-06 18:52:52 |
Message-ID: | 20180606185252.abncl7f7utu2j7k3@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Schneider | 2018-06-06 23:27:08 | Re: BUG #14820: Standby crash with "could not access status of transaction" (for track_commit_timestamp) |
Previous Message | Frits Jalvingh | 2018-06-06 17:13:29 | Re: BUG #15225: [XX000] ERROR: invalid DSA memory alloc request size 1073741824 / Where: parallel worker |