pgsql: Revert ECPG's use of pnstrdup() - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Revert ECPG's use of pnstrdup()
Date
Msg-id E1sbwJX-003EFo-RV@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Revert ECPG's use of pnstrdup()

Commit 0b9466fce added a dependency on fe_memutils' pnstrdup() inside
informix.c.  This adds an exit() path in a library, which we don't
want.  (Unlike libpq, the ecpg libraries don't have an automated check
for that, but it makes sense to keep them to a similar standard.)  The
ecpg code can already handle failure results from the *strdup() call
by itself.

Author: Jacob Champion <jacob.champion@enterprisedb.com>
Discussion: https://www.postgresql.org/message-id/CAOYmi+=pg=W5L1h=3MEP_EB24jaBu2FyATrLXqQHGe7cpuvwyg@mail.gmail.com

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/ee2997c678d86568328f0221717676f86b8aa6f6

Modified Files
--------------
src/interfaces/ecpg/compatlib/informix.c | 23 +++++++++++++++++++++--
1 file changed, 21 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: pgsql: Introduce hash_search_with_hash_value() function
Next
From: Heikki Linnakangas
Date:
Subject: pgsql: Fix pg_rewind debug output to print the source timeline history