Re: cannot abort transaction 2737414167, it was already committed

On Wed, Dec 27, 2023 at 09:02:25AM -0600, Justin Pryzby wrote:
> We had this:
> 
> < 2023-12-25 04:06:20.062 MST telsasoft >ERROR:  could not open file
"pg_tblspc/16395/PG_16_202307071/16384/121010871":Input/output error
 
> < 2023-12-25 04:06:20.062 MST telsasoft >STATEMENT:  commit
> < 2023-12-25 04:06:20.062 MST telsasoft >WARNING:  AbortTransaction while in COMMIT state
> < 2023-12-25 04:06:20.062 MST telsasoft >PANIC:  cannot abort transaction 2737414167, it was already committed
> < 2023-12-25 04:06:20.473 MST  >LOG:  server process (PID 14678) was terminated by signal 6: Aborted

> It's possible that the filesystem had an IO error, but I can't find any
> evidence of that.  Postgres is running entirely on zfs, which says:

FYI: the VM which hit this error also just hit:

log_time               | 2024-01-07 05:19:11.611-07
error_severity         | ERROR
message                | could not open file "pg_tblspc/16395/PG_16_202307071/16384/123270438_vm": Input/output error
query                  | commit
location               | mdopenfork, md.c:663

Since I haven't seen this anywhere else, that's good evidence it's an
issue with the backing storage (even though the FS/kernel aren't nice
enough to say so).

-- 
Justin