| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: hung backends stuck in spinlock heavy endless loop |
| Date: | 2015-01-14 23:38:45 |
| Message-ID: | CAHyXU0w17f6tL7Z9+EPeA4ZpOjgoNj8sgDMJ0jWhcPjXdp=_Ew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 14, 2015 at 2:32 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Wed, Jan 14, 2015 at 12:24 PM, Peter Geoghegan <pg(at)heroku(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-01-14 23:39:45 | Re: hung backends stuck in spinlock heavy endless loop |
| Previous Message | Kouhei Kaigai | 2015-01-14 23:02:56 | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |