Postgres Pro
Downloads
Home   >   mailing lists

pgsql: Do a CHECK_FOR_INTERRUPTS after emitting a message of less than - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Do a CHECK_FOR_INTERRUPTS after emitting a message of less than
Date
Msg-id 20061001220818.82DA49FB32B@postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
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:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: date_trunc also accepts 'quarter'.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Make some marginal performance improvements in