Re: Add comment explaining why queryid is int64 in pg_stat_statements - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Add comment explaining why queryid is int64 in pg_stat_statements
Date
Msg-id aCwOeWZrunWikI4d@paquier.xyz
Whole thread Raw
In response to Re: Add comment explaining why queryid is int64 in pg_stat_statements  (Ilia Evdokimov <ilya.evdokimov@tantorlabs.com>)
Responses Re: Add comment explaining why queryid is int64 in pg_stat_statements
List pgsql-hackers
On Mon, May 19, 2025 at 08:43:25PM -0700, Lukas Fittl wrote:
> Yeah, +1 to making this consistent across both query ID and the new plan
> ID, and changing both to int64 internally seems best.

Any thoughts from others?  I'm OK to take the extra step of switching
both fields on HEAD and write a patch for that, relying on what David
has sent as a first step towards that.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Conflict detection for update_deleted in logical replication
Next
From: Tatsuo Ishii
Date:
Subject: Re: Adding null patch entry to cfbot/CommitFest