Re: Fix out-of-bounds in the function GetCommandTagName
Ranier Vilela <ranier.vf@gmail.com>
From: Ranier Vilela <ranier.vf@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Rowley <dgrowleyml@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2024-05-13T18:02:05Z
Lists: pgsql-hackers
Em seg., 13 de mai. de 2024 às 14:38, Tom Lane <tgl@sss.pgh.pa.us> escreveu: > David Rowley <dgrowleyml@gmail.com> writes: > > I've added a CF entry under your name for this: > > https://commitfest.postgresql.org/48/4927/ > > > If it was code new to PG17 I'd be inclined to go ahead with it now, > > but it does not seem to align with making the release mode stable. > > I'd bet others will feel differently about that. Delaying seems a > > better default choice at least. > > The security team's Coverity instance has started to show this > complaint now too. So I'm going to go ahead and push this change > in HEAD. It's probably unwise to change it in stable branches, > since there's at least a small chance some external code is using > COMMAND_TAG_NEXTTAG for the same purpose tag_behavior[] does. > But we aren't anywhere near declaring v17's API stable, so > I'd rather fix the issue than dismiss it in HEAD. > Thanks for the commit, Tom. best regards, Ranier Vilela
Commits
-
Remove COMMAND_TAG_NEXTTAG from enum CommandTag.
- 1f7452fa598e 17.0 landed