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
Hm. I would imagine that as soon as this process does something,
the messages stop? (It should close i
... 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.
Hm ... there simply isn't a
"Thomas H." <[EMAIL PROTECTED]> writes:
> ... 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 WSA
"Thomas H." <[EMAIL PROTECTED]> writes:
>> 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
Hm. I would imagine that as soon as this process does someth
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
20
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 relat
"Thomas H." <[EMAIL PROTECTED]> writes:
> 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
> 200
Here's a few seconds of the log output (this has been going on for 10
mins as of this e-mail being sent):
2006-11-28 16:16:10 LOG: could not fsync segment 0 of relation
1663/16404/30267: Permission denied
2006-11-28 16:16:10 ERROR: storage sync failed on magnetic disk:
Permission denied
Here'
On Fri, Dec 01, 2006 at 20:41:32 +,
Albert Strasheim <[EMAIL PROTECTED]> wrote:
>
> Description:Feature request: tinyint and unsigned types
You can already use "char" to store 1 byte values, though unless there are
several of these in a row, you won't save any space because of align
On Friday 01 December 2006 19:52, you wrote:
> Igor Shevchenko <[EMAIL PROTECTED]> writes:
> > I've been using partial PGresult-s since pgsql v7.4, and one of "signs"
> > that it's there (after a "read" event on a non-blocking tcp connection to
> > pgsql + a call to PQconsumeInput) is a check: "pgc
10 matches
Mail list logo
