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

Re: postmaster.pid

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Barry Lind" <blind(at)xythos(dot)com>,<pgsql-hackers-win32(at)postgresql(dot)org>
Cc: "Max Dunn" <mdunn(at)xythos(dot)com>
Subject: Re: postmaster.pid
Date: 2004-08-20 22:59:36
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E41A7801@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
 


________________________________

	From: pgsql-hackers-win32-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org] On Behalf Of Dave Page
	Sent: 20 August 2004 20:57
	To: Barry Lind; pgsql-hackers-win32(at)postgresql(dot)org
	Cc: Max Dunn
	Subject: Re: [pgsql-hackers-win32] postmaster.pid 
	
	
	 
	 
	I've been thinking about this problem as well, and think you
might just be on to something here. I'll look into this some more...
	 

The correct way to do this is MoveFileEx("postmaster.pid", NULL,
MOVEFILE_DELAY_UNTIL_REBOOT);. This /should/ write a registry entry to
tell the system to delete the file at reboot. Unfortunately, it seems
that this is an administrator-only operation which of course means it
won't work when run under the postgresql service account.
 
Regards, Dave.

Responses

pgsql-hackers-win32 by date

Next:From: Dave PageDate: 2004-08-20 23:08:30
Subject: Re: Service startup delay
Previous:From: Dave PageDate: 2004-08-20 19:56:42
Subject: Re: postmaster.pid

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