| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: infinite loop in _bt_getstackbuf |
| Date: | 2014-10-31 14:29:53 |
| Message-ID: | CA+TgmobU-hZc-dKWWjeaL4yW2+3gbCUC38F07FW5E8L3X=kU7A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 30, 2014 at 11:45 PM, Noah Misch <noah(at)leadboat(dot)com> wrote:
>> Given the lack of prior complaints about this
>> loop, I'm not sure I see the need to work harder than that; corruption
>> of this sort must be quite rare.
>
> Looks like _bt_getstackbuf() is always called with some buffer lock held, so
> CHECK_FOR_INTERRUPTS() alone would not help:
>
> http://www.postgresql.org/message-id/flat/16519(dot)1401395152(at)sss(dot)pgh(dot)pa(dot)us
That's the insert path. What about the vacuum path?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2014-10-31 14:31:29 | Re: tracking commit timestamps |
| Previous Message | Mark Woodward | 2014-10-31 14:28:00 | CREATE INDEX CONCURRENTLY? |