Re: [HACKERS] 64-bit queryId?
От | Joshua D. Drake |
---|---|
Тема | Re: [HACKERS] 64-bit queryId? |
Дата | |
Msg-id | 03aedcb2-1331-42d1-797c-e35c656918de@commandprompt.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] 64-bit queryId? (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [HACKERS] 64-bit queryId?
Re: [HACKERS] 64-bit queryId? |
Список | pgsql-hackers |
On 10/01/2017 04:22 PM, Robert Haas wrote: > On Sun, Oct 1, 2017 at 3:48 PM, Greg Stark <stark@mit.edu> wrote: >> Well these kinds of monitoring systems tend to be used by operations >> people who are a lot more practical and a lot less worried about >> theoretical concerns like that. > > +1, well said. > >> In context the point was merely that the default >> pg_stat_statements.max of 5000 isn't sufficient to argue that 32-bit >> values are enough. It wouldn't be hard for there to be 64k different >> queries over time and across all the databases in a fleet and at that >> point it becomes likely there'll be a 32-bit collision. > > Yeah. > > I think Alexander Korotkov's points are quite good, too. > +1 to both of these as well. jD -- Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc PostgreSQL Centered full stack support, consulting and development. Advocate: @amplifypostgres || Learn: https://pgconf.us ***** Unless otherwise stated, opinions are my own. ***** -- 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 по дате отправления: