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

Re: fork/exec patch: pre-CreateProcess finalization

From: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
To: 'Tom Lane ' <tgl(at)sss(dot)pgh(dot)pa(dot)us>,'Jan Wieck ' <JanWieck(at)Yahoo(dot)com>
Cc: 'Bruce Momjian ' <pgman(at)candle(dot)pha(dot)pa(dot)us>,Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>,"''''pgsql-patches(at)postgresql(dot)org' ' ' '" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: fork/exec patch: pre-CreateProcess finalization
Date: 2004-01-09 02:48:25
Message-ID: A02DEC4D1073D611BAE8525405FCCE2B55F23B@harris.memetrics.local (view raw or flat)
Thread:
Lists: pgsql-patches
Tom Lane writes:
> Actually, on further reflection a separate array to store PIDs and
cancel keys is probably a better idea.  
[snip]
> I still think it's unnecessary to make a separate shmem segment for it,
though.

Why is that? Don't we need the backends to have access to it to do a cancel
request? I think I've missed something here...

Claudio


--- 
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see 
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>

Responses

pgsql-patches by date

Next:From: Bruce MomjianDate: 2004-01-09 02:52:42
Subject: Re: fork/exec patch: pre-CreateProcess finalization
Previous:From: Jan WieckDate: 2004-01-09 02:46:54
Subject: Re: fork/exec patch: pre-CreateProcess finalization

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