]> granicus.if.org Git - postgresql/commit
Do a CHECK_FOR_INTERRUPTS after emitting a message of less than ERROR
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 1 Oct 2006 22:08:18 +0000 (22:08 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 1 Oct 2006 22:08:18 +0000 (22:08 +0000)
commit8e4fe3ba1ed8aa6bfa59b99555d67a864a2bee84
tree1319f60a973fd50f4765e8d05ddb9ad1ad465ae2
parente69c09c1e946f5a656d1a89a3679e1480762f172
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.
src/backend/utils/error/elog.c