| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov> |
| Cc: | "Thomas H(dot)" <me(at)alternize(dot)com>, pgsql-bugs(at)postgresql(dot)org, Magnus Hagander <mha(at)sollentuna(dot)net> |
| Subject: | Re: BUG #2712: could not fsync segment: Permission |
| Date: | 2006-10-23 19:47:14 |
| Message-ID: | 27795.1161632834@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
"Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov> writes:
> FWIW, we were bitten by the fsync problem which you noticed too.
> Unfortunately we were never able to track down a cause (see the mailing
> list archives). They are separate problems though.
Actually, now that I look back in the archives, I think we had theorized
that the fsync errors come from attempting to fsync a file that's
already been deleted but some backend still has a reference to.
Apparently that leads to EACCES instead of ENOENT (which the code is
already prepared to expect).
http://archives.postgresql.org/pgsql-bugs/2006-04/msg00215.php
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas H. | 2006-10-23 20:49:37 | Re: BUG #2712: could not fsync segment: Permission |
| Previous Message | Peter Brant | 2006-10-23 19:24:25 | Re: BUG #2712: could not fsync segment: Permission |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2006-10-23 19:57:51 | Re: COPY does not work with regproc and aclitem |
| Previous Message | Zdenek Kotala | 2006-10-23 19:43:47 | COPY does not work with regproc and aclitem |