Thread: pgsql: Do a CHECK_FOR_INTERRUPTS after emitting a message of less than

pgsql: Do a CHECK_FOR_INTERRUPTS after emitting a message of less than

From

tgl@postgresql.org (Tom Lane)

Date:

01 October 2006, 19:08:22

Log Message:
-----------
Do a CHECK_FOR_INTERRUPTS after emitting a message of less than ERROR
severity.  This is to ensure the user can cancel a query that's spitting
out lots of notice/warning messages, even if they're coming from a loop
that doesn't otherwise contain a CHECK_FOR_INTERRUPTS.  Per gripe from
Stephen Frost.

Modified Files:
--------------
    pgsql/src/backend/utils/error:
        elog.c (r1.174 -> r1.175)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/error/elog.c.diff?r1=1.174&r2=1.175)