| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | joanaliang_05(at)126(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15221: Could not open file "pg_subtrans/0013" |
| Date: | 2018-05-31 13:50:04 |
| Message-ID: | 3852.1527774604@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> 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.
EINVAL on a file open is pretty uncommon ...
> the database data is mounted and stored to a NFS folder.
... but I've heard of it happening with unstable NFS setups.
You might check for NFS version compatibility, firewalls blocking
some of the ports NFS uses, etc.
But really my advice would be "don't access your database over NFS".
It's just not reliable enough.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-05-31 16:39:01 | BUG #15222: pg_isready fails connection after previous pg_isready claims success |
| Previous Message | PG Bug reporting form | 2018-05-31 06:41:28 | BUG #15221: Could not open file "pg_subtrans/0013" |