Ranier Vilela <ranier.vf@gmail.com> writes: > msvc 2019 (64 bits), is worried about it: > C:\dll\postgres\src\backend\utils\adt\dbsize.c(630,20): warning C4334: > '<<': resultado de 32-bit shift convertido implicitamente para 64 bits > (64-bit shift era pretendid > o?) [C:\dll\postgres\postgres.vcxproj] Yeah, most/all of the MSVC buildfarm members are showing this warning too. The previous coding was Int64GetDatum((int64) (1 << count)) which apparently is enough to silence MSVC, though it makes no difference as to the actual overflow risk involved. I'm a bit inclined to make the new code be NumericGetDatum(int64_to_numeric(INT64CONST(1) << count));
pgsql-hackers by date:
Соглашаюсь с условиями обработки персональных данных