From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Schindler <pschindler(at)synchronicity(dot)com> |
Cc: | pg-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: stuck spinlock |
Date: | 2001-02-27 02:31:07 |
Message-ID: | 27555.983241067@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Schindler <pschindler(at)synchronicity(dot)com> writes:
> FATAL: s_lock(fcc01067) at xlog.c:2088, stuck spinlock. Aborting.
Judging from the line number, this is in CreateCheckPoint. I'm
betting that your platform (Solaris 2.7, you said?) has the same odd
behavior that I discovered a couple days ago on HPUX: a select with
a delay of tv_sec = 0, tv_usec = 1000000 doesn't delay 1 second like
a reasonable person would expect, but fails instantly with EINVAL.
This causes the spinlock timeout in CreateCheckPoint to effectively
be only a few microseconds rather than the intended ten minutes.
So, if the postmaster happens to fire off a checkpoint process while
some regular backend is doing something with the WAL log, kaboom.
In short: please try the latest nightly snapshot (this fix is since
beta5, unfortunately) and let me know if you still see a problem.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2001-02-27 03:00:05 | Re[2]: Re: [PATCHES] A patch for xlog.c |
Previous Message | jamexu | 2001-02-27 02:27:22 | Re[2]: Re: [PATCHES] A patch for xlog.c |