| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-09-30 16:25:04 |
| Message-ID: | CA+TgmobgPRWAskapWyVv87he+1TBhFZDrwHBMpK3djgFJzkHow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Sep 30, 2017 at 12:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> More to the point: with 32-bit IDs, it's apparent that you shouldn't
> really rely on them being unique, and should design your usage so that
> it will survive collisions.
But the point is precisely that we do not do that. pg_stat_statements
"survives" collisions, but nothing good happens.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2017-09-30 16:47:06 | Re: Re: CREATE COLLATION does not sanitize ICU's BCP 47 language tags. Should it? |
| Previous Message | Andres Freund | 2017-09-30 16:06:19 | Re: 64-bit queryId? |