Re: [HACKERS] 64-bit queryId?

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] 64-bit queryId?
Дата
Msg-id 555.1506979950@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] 64-bit queryId?  (Peter Geoghegan <pg@bowt.ie>)
Ответы Re: [HACKERS] 64-bit queryId?  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Список pgsql-hackers
Peter Geoghegan <pg@bowt.ie> writes:
> You need to change the SQL interface as well, although I'm not sure
> exactly how. The problem is that you are now passing a uint64 queryId
> to Int64GetDatumFast() within pg_stat_statements_internal(). That
> worked when queryId was a uint32, because you can easily represent
> values <= UINT_MAX as an int64/int8. However, you cannot represent the
> second half of the range of uint64 within a int64/int8. I think that
> this will behave different depending on USE_FLOAT8_BYVAL, if nothing
> else.

Maybe intentionally drop the high-order bit, so that it's a 63-bit ID?
        regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: [HACKERS] [sqlsmith] stuck spinlock in pg_stat_get_wal_receiverafter OOM
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] [sqlsmith] stuck spinlock in pg_stat_get_wal_receiver after OOM