Postgres Pro
Downloads
Home   >   mailing lists

pgsql: FATAL errors are meant to stop ecpg immediately, e.g. - Mailing list pgsql-committers

From meskes@postgresql.org (Michael Meskes)
Subject pgsql: FATAL errors are meant to stop ecpg immediately, e.g.
Date
Msg-id 20100402102746.1C1F47541D0@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
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)

pgsql-committers by date:

Previous
From: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: Don't pass an invalid file handle to dup2().
Next
From: sriggs@postgresql.org (Simon Riggs)
Date:
Subject: pgsql: Move system startup message prior to any calls out of data