Postgres Pro
Downloads
Home   >   mailing lists

Re: CHECK_FOR_INTERRUPTS in spgdoinsert() isn't helpful - Mailing list pgsql-hackers

From Tom Lane
Subject Re: CHECK_FOR_INTERRUPTS in spgdoinsert() isn't helpful
Date
Msg-id 16847.1401396151@sss.pgh.pa.us
Whole thread Raw
In response to Re: CHECK_FOR_INTERRUPTS in spgdoinsert() isn't helpful  (Peter Geoghegan <pg@heroku.com>)
Responses Re: CHECK_FOR_INTERRUPTS in spgdoinsert() isn't helpful  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
Tree view 
Peter Geoghegan <pg@heroku.com> writes:
> On Thu, May 29, 2014 at 1:34 PM, Heikki Linnakangas
> <hlinnakangas@vmware.com> wrote:
>> Also checking that CritSectionCount == 0 seems like a good idea...

> What do you do if it isn't?

Not throw the error.  (If we did, it'd turn into a PANIC, which doesn't
seem like what we want.)
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: CHECK_FOR_INTERRUPTS in spgdoinsert() isn't helpful
Next
From: Claudio Freire
Date:
Subject: Re: Extended Prefetching using Asynchronous IO - proposal and patch