Re: [HACKERS] 64-bit queryId? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] 64-bit queryId?
Date
Msg-id CA+Tgmoam6mhVni5iEc85FSLRYd0rfdKy221tOETKfave3d52_A@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] 64-bit queryId?  (Greg Stark <stark@mit.edu>)
Responses Re: [HACKERS] 64-bit queryId?
Re: [HACKERS] 64-bit queryId?
List pgsql-hackers
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
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 by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: [HACKERS] Crash on promotion when recovery.conf is renamed
Next
From: Daniel Gustafsson
Date:
Subject: Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem