pgsql-server: Fix oversight: there's no reason for PG_TRY to use

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql-server: Fix oversight: there's no reason for PG_TRY to use
Date: 2004-09-16 21:59:24
Message-ID: 20040916215924.5C1C3329E1C@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix oversight: there's no reason for PG_TRY to use sigsetjmp(buf,1)
since we don't change the signal mask during normal backend operations.
Use sigsetjmp(buf,0) to avoid many unnecessary kernel calls.

Modified Files:
--------------
pgsql-server/src/include/utils:
elog.h (r1.76 -> r1.77)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/include/utils/elog.h.diff?r1=1.76&r2=1.77)

Browse pgsql-committers by date

  From Date Subject
Next Message Joe Conway 2004-09-16 23:30:33 pgsql-server: Make discovery of python_configdir architecture
Previous Message Tom Lane 2004-09-16 21:20:21 pgsql-server: Remove contrib/pg_logger, per recent discussion.