| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
| Cc: | "pgsql-hackers-win32" <pgsql-hackers-win32(at)postgresql(dot)org> |
| Subject: | Re: pqsignal - to be or (in this case) not to be |
| Date: | 2004-02-04 23:38:18 |
| Message-ID: | 23028.1075937898@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
>> Put it into the macro that checks for query cancel.
> Are there other places that you know offhand that we should check for
> signals?
I'd like to think that that is the only place. There are places in the
code where we need to insert more cancel checks (I think the planner is
missing a few for instance) but there is not any justification for
cluttering things with a Windows-specific addition.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Natoli | 2004-02-05 01:17:41 | Re: win32 signals, part 4 |
| Previous Message | Magnus Hagander | 2004-02-04 23:34:08 | Re: pqsignal - to be or (in this case) not to be |