Re: [pgsql-hackers-win32] Win32 signal code - first try - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: [pgsql-hackers-win32] Win32 signal code - first try
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE2A6B42@algol.sollentuna.se
Whole thread Raw
List pgsql-hackers
> > 1. setjmp/longjmp stack manipulation (i.e. ELOG)
>
> Wrote a small program to check this out. As we
> hoped/assumed/expected, it looks just fine.
Great!
Just checking - we're talking doing this from inside a user APC, right?

> Magnus, are you working on a second run at this stuff?

Not right this moment, but I hope to do that sometime this weekend. (No
time until then).


A thought there. If we go with the "select loop" version you had tried
out and just poll (select() with short timeout, poll, loop..), do we
actually *need* the APCs *at all*? Or should we go with a pure-polling
solution? (With signals delivered on a separate thread as we discussed,
of course) The only advantage we gain by the APCs is that they will stop
the "Ex functions", no? (It's not much extra code to put it in there,
but if we don't need it..)


//Magnus


pgsql-hackers by date:

Previous
From: jihuang
Date:
Subject: FYI , Intel CC and PostgreSQL , benchmark by pgsql
Next
From: ohp@pyrenet.fr
Date:
Subject: set search_path and pg_dumpall