Re: Non-decimal integer literals
От | David Rowley |
---|---|
Тема | Re: Non-decimal integer literals |
Дата | |
Msg-id | CAApHDvoqToAG_At7gBZNSD1PaadRfS40gP3JraGBY76As-t5Ow@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Non-decimal integer literals (Peter Eisentraut <peter.eisentraut@enterprisedb.com>) |
Ответы |
Re: Non-decimal integer literals
|
Список | pgsql-hackers |
On Thu, 24 Nov 2022 at 21:35, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote: > My code follows the style used for parsing the decimal integers. > Keeping that consistent is valuable I think. I think the proposed > change makes the code significantly harder to understand. Also, what > you are suggesting here would amount to an attempt to make parsing > hexadecimal integers even faster than parsing decimal integers. Is that > useful? Isn't it being faster one of the major use cases for this feature? I remember many years ago and several jobs ago when working with SQL Server being able to speed up importing data using hexadecimal DATETIMEs. I can't think why else you might want to represent a DATETIME as a hexstring, so I assumed this was a large part of the use case for INTs in PostgreSQL. Are you telling me that better performance is not something anyone will want out of this feature? David
В списке pgsql-hackers по дате отправления: