Re: ESQL/C no indicator variables ./. error -213 - Mailing list pgsql-general

From Tom Lane
Subject Re: ESQL/C no indicator variables ./. error -213
Date
Msg-id 1451504.1592415593@sss.pgh.pa.us
Whole thread Raw
In response to ESQL/C no indicator variables ./. error -213  (Matthias Apitz <guru@unixarea.de>)
Responses Re: ESQL/C no indicator variables ./. error -213  (Matthias Apitz <guru@unixarea.de>)
List pgsql-general
Matthias Apitz <guru@unixarea.de> writes:
> We encountered that if our ESQL/C written servers see on SELECT or FETCH
> in a row a NULL value, it will raise correctly the error -213 as written
> and explained in https://www.postgresql.org/docs/11/ecpg-variables.html#ECPG-INDICATORS
> We catch this error -213 and deal with in.

> What we did not knew and discovered today is something very fatal: In
> such a situation on a FETCH of a row of some 55 columns, the transfer of
> the column elements into their hostvariables stops on first NULL value,
> as here to be seen in the log:

Could you provide a self-contained test case for this?  It's hard to
guess at what the problem might be.

            regards, tom lane



pgsql-general by date:

Previous
From: Matthias Apitz
Date:
Subject: ESQL/C no indicator variables ./. error -213
Next
From: "Jim Hurne"
Date:
Subject: RE: autovacuum failing on pg_largeobject and disk usage of thepg_largeobject growing unchecked