Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> You had a near-identical complaint about a compiler warning that led
> to my commit d64f1cdf2f4 -- that one involved _bt_check_unique()'s
> curitup, while this one is about curitemid. While I have no problem
> silencing this compiler warning now, I don't see any reason to not
> just do the same thing again. Which is to initialize the pointer to
> NULL.
Works for me; if there is any bug in the logic, we'll get a core dump
and can investigate.
regards, tom lane