| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matthias Apitz <guru(at)unixarea(dot)de> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ESQL/C no indicator variables ./. error -213 |
| Date: | 2020-06-17 17:39:53 |
| Message-ID: | 1451504.1592415593@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Matthias Apitz <guru(at)unixarea(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Hurne | 2020-06-17 18:26:24 | RE: autovacuum failing on pg_largeobject and disk usage of the pg_largeobject growing unchecked |
| Previous Message | Matthias Apitz | 2020-06-17 17:02:21 | ESQL/C no indicator variables ./. error -213 |