Richard van den Berg <richard.vandenberg@trust-factory.com> writes:
> Is there a good reason that the official RPM on postgresql.org is not
> build with HAVE_INT64_TIMESTAMP ? It would have been so nice if this
> would have worked. :-/
You've got that 100% backwards: you should be complaining to Debian that
it's not their business to editorialize on the default setting.
regards, tom lane
Hi Stephen! Stephen Frost [2005-12-13 11:06 -0500]: > Honestly, in the end I think the default should be changed. It could > fall-back to double with a warning (if it doesn't already) if the > compiler doesn't support 64bit integers. > [...] > I don't think the Debian default should be changed though. If, say, an > m68k user actually complained about the default not being the right > option for them then I'd say we should consider having configure options > be different for those architectures and not that we should move > everyone to using doubles. I fully agree. (BTW, I doubt that double operations on m68k would be any faster than integer ones...) Thanks, Martin -- Martin Pitt http://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org In a world without walls and fences, who needs Windows and Gates?
Martin Pitt <martin@piware.de> writes:
> I fully agree. (BTW, I doubt that double operations on m68k would be
> any faster than integer ones...)
Debatable at best --- most later 68k machines had hardware FPUs, but
none of them had any 64-bit-int instructions...
regards, tom lane
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера