8.3RC1 on windows missing descriptive Event handle names
On Windows XP, using Process Explorer with the lower pane showing Handles, not all postgres.exe processes are including an "Event" type with a description of what the process is doing.
At the moment, I have ten postgres processes shown as being at the bottom of the tree, three of which do not have such descriptions.
The processes that do show an Event type handle show these names:
\BaseNamedObjects\pgident: postgres: wal writer process
\BaseNamedObjects\pgident: postgres: autovacuum launcher process
plus one per connection like:
\BaseNamedObjects\pgident: postgres: postgres mydatabase 127.0.0.1(1954) idle
Comparing the list of processes to those of 8.2, I suspect that the processes missing this detail are the log writer (one of the processes does have a File Handle on the log file), and the stats collector.
I have autovacuum enabled for 8.3rc1, and disabled for 8.2.
PostgreSQL is started as a service.
Stephen Denne
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer focus, and courage. This email with any attachments is confidential and may be subject to legal privilege. If it is not intended for you please advise by reply immediately, destroy it and do not copy, disclose or use it in any way.
__________________________________________________________________
This email has been scanned by the DMZGlobal Business Quality
Electronic Messaging Suite.
Please see http://www.dmzglobal.com/services/bqem.htm for details.
__________________________________________________________________
I said...
On Windows XP, using Process Explorer with the lower pane
showing Handles, not all postgres.exe processes are including
an "Event" type with a description of what the process is doing.
I've had difficulty reproducing this, but I now suspect that it is only happening when running both v8.2 and v8.3rc1 at once, and I think it is the second started that is missing the process descriptions.
Regards,
Stephen Denne.
Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer focus, and courage. This email with any attachments is confidential and may be subject to legal privilege. If it is not intended for you please advise by reply immediately, destroy it and do not copy, disclose or use it in any way.
__________________________________________________________________
This email has been scanned by the DMZGlobal Business Quality
Electronic Messaging Suite.
Please see http://www.dmzglobal.com/services/bqem.htm for details.
__________________________________________________________________
Stephen Denne wrote:
I said...
On Windows XP, using Process Explorer with the lower pane showing
Handles, not all postgres.exe processes are including an "Event"
type with a description of what the process is doing.I've had difficulty reproducing this, but I now suspect that it is
only happening when running both v8.2 and v8.3rc1 at once, and I
think it is the second started that is missing the process
descriptions.
That makes sense, really - I think you nailed it. We create a global
event, and for those that are "duplicates", it won't show up in the
second process.
I think the solution to this is to add the process id to the name of the
event. So instead of:
pgident: postgres: autovacuum launcher process
We'd ahve
pgident(12345): postgres: autovacuum launcher process
Seems reasomable? I'll be able to write up and properly test a patch
tomorrow.
//Magnus
On Wed, Jan 30, 2008 at 09:59:38PM +0100, Magnus Hagander wrote:
Stephen Denne wrote:
I said...
On Windows XP, using Process Explorer with the lower pane showing
Handles, not all postgres.exe processes are including an "Event"
type with a description of what the process is doing.I've had difficulty reproducing this, but I now suspect that it is
only happening when running both v8.2 and v8.3rc1 at once, and I
think it is the second started that is missing the process
descriptions.That makes sense, really - I think you nailed it. We create a global
event, and for those that are "duplicates", it won't show up in the
second process.I think the solution to this is to add the process id to the name of the
event. So instead of:
pgident: postgres: autovacuum launcher process
We'd ahve
pgident(12345): postgres: autovacuum launcher processSeems reasomable? I'll be able to write up and properly test a patch
tomorrow.
I've applied a patch for this to HEAD and 8.2. It will be in the 8.3
release and in the next release of 8.2 when it's ready. It should be enough
that *one* of the two installations has the patch for the fix to work, so
8.3 release vs your current 8.2 should still work.
//Magnus