Re: Potential issue in ecpg-informix decimal converting functions
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Michael Paquier <michael@paquier.xyz>
Cc: a.imamov@postgrespro.ru,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-02-25T23:28:51Z
Lists: pgsql-hackers
> On 24 Feb 2024, at 02:15, Michael Paquier <michael@paquier.xyz> wrote: > > On Fri, Feb 23, 2024 at 06:03:41PM +0300, a.imamov@postgrespro.ru wrote: >> Thank's for advice, the patch will be registered for the next commitfest. > > The risk looks really minimal to me, but playing with error codes > while the logic of the function is unchanged does not strike me as > something to backpatch as it could slightly break applications. On > HEAD, I'm OK with that. Yeah, I think this is for HEAD only, especially given the lack of complaints against backbranches. -- Daniel Gustafsson
Commits
-
doc: Document error handling in PGTYPESnumeric_to_long
- 68174679fea2 17.0 landed
-
ecpg: Fix return code for overflow in numeric conversion
- b2d6b4c728a2 17.0 landed