| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Peter Geoghegan <pg(at)bowt(dot)ie>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 64-bit queryId? |
| Date: | 2017-10-01 23:22:20 |
| Message-ID: | CA+Tgmoam6mhVni5iEc85FSLRYd0rfdKy221tOETKfave3d52_A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Oct 1, 2017 at 3:48 PM, Greg Stark <stark(at)mit(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2017-10-01 23:36:17 | Re: Vacuum: allow usage of more than 1GB of work mem |
| Previous Message | Daniel Gustafsson | 2017-10-01 23:13:59 | Re: Crash on promotion when recovery.conf is renamed |