Re: overflow bug for inhcounts
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: jian he <jian.universality@gmail.com>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-10-10T16:38:36Z
Lists: pgsql-hackers
On 2024-Oct-09, jian he wrote: > CreateConstraintEntry(const char *constraintName, > we can change > int conInhCount, > to > int16 conInhCount. > doing that, meaning we also need to refactor some of the caller functions. Good thought, thanks. > we can also change > node Constraint field inhcount from int to int16. Nah, that field is unused, so I removed it. I gave another look at the not-nulls branch, and we can do without it. This is pushed, although there was a technical glitch (since fixed by Magnus Hagander) and the pgsql-committers message was not sent. But you can see it here: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=fd64ed60b62697984bb69a09a3ae19fbe2905eb6 -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
Commits
-
Unbreak overflow test for attinhcount/coninhcount
- fd64ed60b626 18.0 landed