Re: Fix out-of-bounds in the function GetCommandTagName

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix out-of-bounds in the function GetCommandTagName
Date: 2024-04-15 01:09:02
Message-ID: CAApHDvqVRGurCQk-9EToqrFJOB1vyRfObFaqnZXoa99OX_KK8Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 15 Apr 2024 at 11:54, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> would this also allow us to get rid of any default:
> cases in switches on command tags?

git grep "case CMDTAG_" does not yield any results.

As far as I understand, we'd only be able to get rid of a default case
if we had a switch that included all CMDTAG* values apart from
COMMAND_TAG_NEXTTAG. If we don't ever switch on CMDTAG values then I
think the answer to your question is "no".

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2024-04-15 01:11:44 Re: Stability of queryid in minor versions
Previous Message David Rowley 2024-04-15 01:00:56 Re: Stability of queryid in minor versions