Re: hung backends stuck in spinlock heavy endless loop
От | Merlin Moncure |
---|---|
Тема | Re: hung backends stuck in spinlock heavy endless loop |
Дата | |
Msg-id | CAHyXU0w17f6tL7Z9+EPeA4ZpOjgoNj8sgDMJ0jWhcPjXdp=_Ew@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: hung backends stuck in spinlock heavy endless loop (Peter Geoghegan <pg@heroku.com>) |
Ответы |
Re: hung backends stuck in spinlock heavy endless loop
|
Список | pgsql-hackers |
On Wed, Jan 14, 2015 at 2:32 PM, Peter Geoghegan <pg@heroku.com> wrote: > On Wed, Jan 14, 2015 at 12:24 PM, Peter Geoghegan <pg@heroku.com> wrote: >> Could you write some code to print out the block number (i.e. >> "BlockNumber blkno") if there are more than, say, 5 retries within >> _bt_moveright()? > > Obviously I mean that the block number should be printed, no matter > whether or not the P_INCOMPLETE_SPLIT() path is taken or not. So you > should just move this to the top of the for(;;) loop, so it's always > available to print: > > BlockNumber blkno = BufferGetBlockNumber(buf); (gdb) print BufferGetBlockNumber(buf) $15 = 9 ..and it stays 9, continuing several times having set breakpoint. merlin
В списке pgsql-hackers по дате отправления: