pgsql: FATAL errors are meant to stop ecpg immediately, e.g.

From: meskes(at)postgresql(dot)org (Michael Meskes)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: FATAL errors are meant to stop ecpg immediately, e.g.
Date: 2010-04-02 10:27:46
Message-ID: 20100402102746.1C1F47541D0@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
FATAL errors are meant to stop ecpg immediately, e.g. because the syntax is
corrupted. This error, however, does is not a compilation problem but a runtime
one, so we can keep compiling but still have to declare ERROR.

Modified Files:
--------------
pgsql/src/interfaces/ecpg/preproc:
type.c (r1.90 -> r1.91)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/type.c?r1=1.90&r2=1.91)

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2010-04-02 13:10:56 pgsql: Move system startup message prior to any calls out of data
Previous Message Heikki Linnakangas 2010-04-01 20:12:43 pgsql: Don't pass an invalid file handle to dup2().