Re: Non-decimal integer literals
От | Peter Eisentraut |
---|---|
Тема | Re: Non-decimal integer literals |
Дата | |
Msg-id | be1205f8-de95-8d69-bcc4-6c769c703f5f@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: Non-decimal integer literals (David Rowley <dgrowleyml@gmail.com>) |
Ответы |
Re: Non-decimal integer literals
|
Список | pgsql-hackers |
On 24.11.22 10:13, David Rowley wrote: > 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? Never thought about it that way. > 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? This isn't about datetimes but about integers.
В списке pgsql-hackers по дате отправления: