Skip site navigation (1) Skip section navigation (2)

Re: [PERFORM] scalability issues on win32

From: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
To: 'Merlin Moncure' <merlin(dot)moncure(at)rcsonline(dot)com>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Win 32 hackers PGSQL <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: [PERFORM] scalability issues on win32
Date: 2004-12-03 01:59:20
Message-ID: E80765D3BE190745B72F81EFB8332AAB014CFA@harold.memetrics.local (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers-win32
Hi Merlin,

> On a probably unrelated note:
> Can some other win32 hacker try the following?
> Download the latest cvs sources from the server and edit configure,
> replacing all instances of '8.0beta5' with '8.0' etc. as is 
> will be when released.  Following that do a full make/make clean.  After 
> that try and start he server with pg_ctl.exe and tell me if it succeeds or

I can confirm this failure.

(in my case at least) pg_ctl is not seeing the full version string of the
postmaster in find_other_exec. This is due to the single call to ReadFile in
pipe_read_line, which is not returning the entire version string (losing all
characters beyond the last decimal point in the version string). A
subsequent call to ReadFile picks up the remainder of the string. I don't
see that we can rely on a single call returning the entire version string.

If someone can run with this, I've attached initial looping changes for
pipe_read_line. However I'm not sure of the correct terminating condition
(gets into a call to ReadFile that never returns; the WaitForSingleObject
appears insufficient as a precondition for ReadFile) and just don't have
time to complete it right now.


Attachment: pipe_read.diff
Description: application/octet-stream (1.8 KB)


pgsql-hackers-win32 by date

Next:From: Andrew DunstanDate: 2004-12-03 02:11:30
Subject: Re: [PERFORM] scalability issues on win32
Previous:From: Bruce MomjianDate: 2004-12-02 23:18:30
Subject: Re: statistics process shutting down

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group