Re: pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ... - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ...
Date
Msg-id 603.1061760065@sss.pgh.pa.us
Whole thread Raw
In response to pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ...  (petere@svr1.postgresql.org (Peter Eisentraut - PostgreSQL))
Responses Re: pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ...  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-committers
petere@svr1.postgresql.org (Peter Eisentraut - PostgreSQL) writes:
> Modified files:
>     doc/src/sgml   : libpq.sgml
>     src/interfaces/ecpg/ecpglib: connect.c error.c
>     src/interfaces/libpq: libpq-fe.h

> Log message:
>     Add macros for error result fields to libpq.

libpq has several internal uses of the error-field codes that perhaps
ought to be converted to use these macros, eg, pqInternalNotice(),
pqGetErrorNotice2(), pqGetErrorNotice3().

More generally, is libpq the right place to declare these?  Shouldn't
we instead put 'em in postgres_ext.h, and teach the backend code to use
'em too?

            regards, tom lane

pgsql-committers by date:

Previous
From: petere@svr1.postgresql.org (Peter Eisentraut - PostgreSQL)
Date:
Subject: pgsql-server/src backend/po/ru.po bin/pg_contr ...
Next
From: petere@svr1.postgresql.org (Peter Eisentraut - PostgreSQL)
Date:
Subject: pgsql-server/src/bin/psql/po de.po