Skip site navigation (1) Skip section navigation (2)

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

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Do a CHECK_FOR_INTERRUPTS after emitting a message of less than
Date: 2006-10-01 22:08:18
Message-ID: 20061001220818.82DA49FB32B@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
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)

pgsql-committers by date

Next:From: Tom LaneDate: 2006-10-01 22:25:49
Subject: pgsql: Make some marginal performance improvements in
Previous:From: Tom LaneDate: 2006-10-01 18:54:57
Subject: pgsql: date_trunc also accepts 'quarter'.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group