Re: fork/exec patch: pre-CreateProcess finalization
| От | Claudio Natoli |
|---|---|
| Тема | Re: fork/exec patch: pre-CreateProcess finalization |
| Дата | |
| Msg-id | A02DEC4D1073D611BAE8525405FCCE2B55F23D@harris.memetrics.local обсуждение исходный текст |
| Ответ на | fork/exec patch: pre-CreateProcess finalization (Claudio Natoli <claudio.natoli@memetrics.com>) |
| Ответы |
Re: fork/exec patch: pre-CreateProcess finalization
|
| Список | pgsql-patches |
I wrote:
> Just to be clear, this would involve turning the BackendList dlllist into
an
> array in shared memory, right? If so, a couple of questions:
Bruce Momjian wrote:
> I assumed a much simpler solution. I thought we would just have:
>
> struct {
> pid_t pid;
> int cancel_key;
> } PidCancel[maxbackend];
>
> in shared memory and we would just sequentially scan looking for a pid
> match? Is that wrong?
Isn't that basically "turning the BackendList dlllist into an array in
shared memory"? And I don't think that an array length of maxbackend is
enough.
Cheers,
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>
В списке pgsql-patches по дате отправления: