diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2024-03-20 09:14:51 +0200 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2024-03-20 09:14:51 +0200 |
| commit | d63d486d6c393817810d0477569fc657c388bfb2 (patch) | |
| tree | de2b5d708f136f52426798c9a1997781f69e51d6 /src/backend/utils/adt/jsonpath_exec.c | |
| parent | 9578393bc513e350e9cbfa4679fc7be7309b41a4 (diff) | |
| download | postgresql-d63d486d6c393817810d0477569fc657c388bfb2.tar.gz postgresql-d63d486d6c393817810d0477569fc657c388bfb2.zip | |
Remove assertions that some compiler say are tautological
To avoid the compiler warnings:
launch_backend.c:211:39: warning: comparison of constant 16 with expression of type 'BackendType' (aka 'enum BackendType') is always true [-Wtautological-constant-out-of-range-compare]
launch_backend.c:233:39: warning: comparison of constant 16 with expression of type 'BackendType' (aka 'enum BackendType') is always true [-Wtautological-constant-out-of-range-compare]
The point of the assertions was to fail more explicitly if someone
adds a new BackendType to the end of the enum, but forgets to add it
to the child_process_kinds array. It was a pretty weak assertion to
begin with, because it wouldn't catch if you added a new BackendType
in the middle of the enum. So let's just remove it.
Per buildfarm member ayu and a few others, spotted by Tom Lane.
Discussion: https://www.postgresql.org/message-id/4119680.1710913067@sss.pgh.pa.us
Diffstat (limited to 'src/backend/utils/adt/jsonpath_exec.c')
0 files changed, 0 insertions, 0 deletions