Prashant Chinnam <[email protected]> writes:
> On patch [1]: I intend to keep strtoi64() there even if
> this lands, because the pgcrypto fix is meant to be
> backpatched to REL_18_STABLE, where strtoint() keeps its
> current behavior, while strtoi64() behaves the same on
> both branches. Happy to follow a different direction if
> committers prefer otherwise.
My thought here is to back-patch the strtoint() change.
I cannot envision any case that that would make worse.
And failing to do so leaves a land-mine for potential
future back-patches of code using strtoint().
regards, tom lane
