| From: | "Thomas H(dot)" <me(at)alternize(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: fsync and semctl errors with 8.1.5/win32 |
| Date: | 2006-12-05 03:23:36 |
| Message-ID: | 00b301c7181c$c0b5f690$0201a8c0@iwing |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>> in 8.2.0 the error messages changed a bit:
>
>> 2006-12-05 03:47:12 [736] LOG: could not fsync segment 0 of relation
>> 1663/16692/2361629: Permission denied
>> 2006-12-05 03:47:12 [736] ERROR: storage sync failed on magnetic disk:
>> Permission denied
>> 2006-12-05 03:47:13 [736] ERROR: could not open relation
>> 1663/16692/2361629: Permission denied
>> 2006-12-05 03:47:14 [736] ERROR: could not open relation
>> 1663/16692/2361629: Permission denied
>
> So what's holding the file open now? It's evidently not the bgwriter.
one of the unnamed postgresql.exe processes from the connection pool:
postgres: db_outnow outnow 127.0.0.1(3384) idle
might be related: in addition to the above messages, the log is now also
flooded by:
2006-12-05 04:16:29 [5196] LOG: could not rename temporary statistics file
"global/pgstat.tmp" to "global/pgstat.stat": A blocking operation was
interrupted by a call to WSACancelBlockingCall.
there is no pgstat.tmp file in global...
- thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas H. | 2006-12-05 03:29:56 | Re: fsync and semctl errors with 8.1.5/win32 |
| Previous Message | Tom Lane | 2006-12-05 03:09:33 | Re: fsync and semctl errors with 8.1.5/win32 |