| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Denis Perchine <dyp(at)perchine(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Quite strange crash |
| Date: | 2001-01-09 19:25:42 |
| Message-ID: | 6293.979068342@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Denis Perchine <dyp(at)perchine(dot)com> writes:
> You will get SIGKILL in most cases.
Well, a SIGKILL will cause the postmaster to shut down and restart the
other backends, so we should be safe if that happens. (Annoyed as heck,
maybe, but safe.)
Anyway, this is looking more and more like the SIGTERM that caused your
vacuum to die must have been done manually.
The CRIT_SECTION code that I'm about to go off and add to spinlocking
should prevent similar problems from happening in 7.1, but I don't think
it's reasonable to try to retrofit that into 7.0.*.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2001-01-09 19:30:43 | Re: [HACKERS] How to print explain using PHP |
| Previous Message | Tom Lane | 2001-01-09 19:22:32 | Re: Quite strange crash |