| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
| Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Stuck spins in current |
| Date: | 2001-03-16 23:38:32 |
| Message-ID: | 29182.984785912@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> writes:
> 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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mikheev, Vadim | 2001-03-17 00:01:48 | RE: Stuck spins in current |
| Previous Message | Mikheev, Vadim | 2001-03-16 23:34:10 | RE: Stuck spins in current |