pgsql: Avoid re-using output variables in new ecpg test case. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Avoid re-using output variables in new ecpg test case.
Date
Msg-id E1kbViX-0005Z1-EK@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Avoid re-using output variables in new ecpg test case.

The buildfarm thinks this leads to memory stomps, though annoyingly
I can't duplicate that here.  The existing code in strings.pgc is
doing something that doesn't seem to be sanctioned at all really
by the documentation, but I'm disinclined to try to make that nicer
right now.  Let's just declare some more output variables in hopes
of working around it.

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/3459f4169ba9665fbc7965165ec4ef83170b748b

Modified Files
--------------
src/interfaces/ecpg/test/expected/preproc-strings.c      | 10 ++++++----
src/interfaces/ecpg/test/expected/preproc-strings.stderr |  4 ++++
src/interfaces/ecpg/test/preproc/strings.h               |  4 +++-
src/interfaces/ecpg/test/preproc/strings.pgc             |  4 ++--
4 files changed, 15 insertions(+), 7 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Doc: small release note updates.
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Fix redundant error messages in client tools