| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ian Lance Taylor <ian(at)airs(dot)com> |
| Cc: | mathijs(at)ilse(dot)nl, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [SQL] PostgreSQL crashes on me :( |
| Date: | 2000-12-18 17:40:32 |
| Message-ID: | 20037.977161232@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
Ian Lance Taylor <ian(at)airs(dot)com> writes:
> Therefore, the scenario you describe is possible, but only if there
> happens to be both a timer interrupt and a SIGCHLD signal within a
> couple of instructions after the select returns.
Right. A small failure window would explain the infrequency of the
symptom.
> Ideally, signal handlers should not make system calls. However, if
> this is impossible, then signal handlers must save and restore errno.
I have just committed fixes to do that in current sources (7.1 branch).
I doubt we're going to make a 7.0.4 release, but if we do then this
ought to be back-patched.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lance Taylor | 2000-12-18 17:58:02 | Re: Re: [SQL] PostgreSQL crashes on me :( |
| Previous Message | Ian Lance Taylor | 2000-12-18 17:33:40 | Re: Re: [SQL] PostgreSQL crashes on me :( |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-12-18 17:54:17 | Re: Best database structure for timely ordered values |
| Previous Message | Ian Lance Taylor | 2000-12-18 17:33:40 | Re: Re: [SQL] PostgreSQL crashes on me :( |