aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2024-12-15 15:50:07 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2024-12-15 15:50:07 -0500
commitbf9165bb0c5cea71e1a9cfa0c584c4d176f6c36f (patch)
tree9a91f5ab346e35167b5b18ac9c6dadcc458cdf64 /src/backend/access/gist/gist.c
parent530f89e648da3a5505920322dcd4e00e15559f66 (diff)
downloadpostgresql-bf9165bb0c5cea71e1a9cfa0c584c4d176f6c36f.tar.gz
postgresql-bf9165bb0c5cea71e1a9cfa0c584c4d176f6c36f.zip
Declare a couple of variables inside not outside a PG_TRY block.
I went through the buildfarm's reports of "warning: variable 'foo' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]". As usual, none of them are live problems according to my understanding of the effects of setjmp/longjmp, to wit that local variables might revert to their values as of PG_TRY entry, due to being kept in registers. But I did happen to notice that XmlTableGetValue's "cstr" variable doesn't need to be declared outside the PG_TRY block at all (thus giving further proof that the -Wclobbered warning has little connection to real problems). We might as well move it inside, and "cur" too, in hopes of eliminating one of the bogus warnings.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions