RE: Stuck spins in current

Поиск
Список
Период
Сортировка
От Mikheev, Vadim
Тема RE: Stuck spins in current
Дата
Msg-id 8F4C99C66D04D4118F580090272A7A234D332E@sectorbase1.sectorbase.com
обсуждение исходный текст
Ответ на Stuck spins in current  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
Ответы Re: Stuck spins in current  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Stuck spins in current  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Stuck spins in current
Следующее
От: Peter Eisentraut
Дата:
Сообщение: pg_upgrade