> 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.