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.
btw: FileMon reports every few seconds:
04:24:28 postgres.exe:736 OPEN D:\DB\postgreSQL.82\data\base\16692\2361629
DELETE PEND Options: Open Access: 0012019F
the time corresponds to the "could not open relation" logentries
i would interpret this as: postgresql pid 736 (bgwriter) is trying to open
the file 2361629 which fails because it is marked as "to be deleted". the
file system operation is pending because another process (from the pgsql
connection pool) is still keeping a handle open.
as it is a connection pool process, it will be "recycled" after a while and
release open handles: everytime the error messages disappear after some
minutes...
- thomas
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
