On Mar 2, 2007, at 4:14 PM, Larry Rosenman wrote:
Any guess on when we'd see an 8.2.4? I have a business reason for
asking.
If history is any guide, probably when a 'reasonably large fix' to
something comes around, though reviewing early 8.1 release history
might prove enlightening...
Jim Nasby [EMAIL PROTECTED] writes:
On Mar 2, 2007, at 4:14 PM, Larry Rosenman wrote:
Any guess on when we'd see an 8.2.4? I have a business reason for
asking.
If history is any guide, probably when a 'reasonably large fix' to
something comes around,
Well, what with Bruce on vacation
On Thursday 01 March 2007 11:57, Tom Lane wrote:
Darcy Buskermolen [EMAIL PROTECTED] writes:
I'm observing high CPU usage (95%) of a 2.6GHz opteron by the stats
collector on an 8.2.3 box investigation has lead me to belive that the
stats file is written a lot more often that once every
On Fri, 2 Mar 2007, Darcy Buskermolen wrote:
On Thursday 01 March 2007 11:57, Tom Lane wrote:
Darcy Buskermolen [EMAIL PROTECTED] writes:
I'm observing high CPU usage (95%) of a 2.6GHz opteron by the stats
collector on an 8.2.3 box investigation has lead me to belive that the
stats file is
On Wednesday 28 February 2007 14:31, Joshua D. Drake wrote:
Joshua D. Drake wrote:
Darcy Buskermolen wrote:
I'm observing high CPU usage (95%) of a 2.6GHz opteron by the stats
collector on an 8.2.3 box investigation has lead me to belive that the
stats file is written a lot more often
Darcy Buskermolen [EMAIL PROTECTED] writes:
I'm observing high CPU usage (95%) of a 2.6GHz opteron by the stats
collector on an 8.2.3 box investigation has lead me to belive that the
stats file is written a lot more often that once every 500ms the
following shows this behavior.
Looks like
Tom Lane wrote:
Darcy Buskermolen [EMAIL PROTECTED] writes:
I'm observing high CPU usage (95%) of a 2.6GHz opteron by the stats
collector on an 8.2.3 box investigation has lead me to belive that the
stats file is written a lot more often that once every 500ms the
following shows this
Andrew Dunstan [EMAIL PROTECTED] writes:
Good catch. I am also a bit dubious about this code:
input_fd.fd = pgStatSock;
input_fd.events = POLLIN | POLLERR;
input_fd.revents = 0;
Hm. The Single Unix Spec saith that POLLERR is ignored in the events
field, but it is not
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Good catch. I am also a bit dubious about this code:
input_fd.fd = pgStatSock;
input_fd.events = POLLIN | POLLERR;
input_fd.revents = 0;
Hm. The Single Unix Spec saith that POLLERR is ignored
Andrew Dunstan [EMAIL PROTECTED] writes:
This might all be OK - I just noticed it as I was looking at the
problem, so I though I'd mention it.
I'm inclined to leave that code alone unless someone can point to a
platform where setting POLLERR in events actually causes a problem.
The pgstat code
Darcy Buskermolen wrote:
I'm observing high CPU usage (95%) of a 2.6GHz opteron by the stats collector
on an 8.2.3 box investigation has lead me to belive that the stats file is
written a lot more often that once every 500ms the following shows this
behavior.
PostgreSQL 8.2.3 on
Joshua D. Drake wrote:
Darcy Buskermolen wrote:
I'm observing high CPU usage (95%) of a 2.6GHz opteron by the stats
collector
on an 8.2.3 box investigation has lead me to belive that the stats file is
written a lot more often that once every 500ms the following shows this
behavior.
I
12 matches
Mail list logo
