From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: Stuck spins in current |
Date: | 2001-03-17 00:01:48 |
Message-ID: | 8F4C99C66D04D4118F580090272A7A234D332E@sectorbase1.sectorbase.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > And you know - I've run same tests on ~ Mar 9 snapshot
> > without any problems.
> >>
> >> That was before I changed the code to pre-fill the file ---
> >> now it takes longer to init a log segment. And we're only
> >> using a plain SpinAcquire, not the flavor with a longer timeout.
>
> > xlog.c revision 1.55 from Feb 26 already had log file
> > zero-filling, so ...
>
> Oh, you're right, I didn't study the CVS log carefully enough. Hmm,
> maybe the control file lock isn't the problem. The abort() in
> s_lock_stuck should have left a core file --- what is the backtrace?
After 10 times increasing DEFAULT_TIMEOUT in s_lock.c
I got abort in xlog.c:626 - waiting for insert_lck.
But problem is near new log file creation code: system
goes sleep just after new one is created.
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Giles Lean | 2001-03-17 00:17:51 | Re: Performance monitor signal handler |
Previous Message | Tom Lane | 2001-03-16 23:38:32 | Re: Stuck spins in current |