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 aDjvGZXFMGMJAAHr@paquier.xyz
Whole thread Raw
In response to Re: Add comment explaining why queryid is int64 in pg_stat_statements  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: Add comment explaining why queryid is int64 in pg_stat_statements
List pgsql-hackers
On Thu, May 29, 2025 at 09:28:35AM -0500, Nathan Bossart wrote:
> On Thu, May 29, 2025 at 01:53:07PM +0900, Michael Paquier wrote:
>> Now, I don't really want to take a leap of faith without the RMT being
>> OK with that now that we are in beta1.
>
> After reading through this thread and the latest patch set, I don't see any
> strong reason for the RMT to object to this change for v18.  IIUC some
> extensions may need to adapt, but we're still a few months from 18.0, so
> that seems okay.  I vaguely recall that we've made other small
> extension-breaking changes during the beta period for previous major
> releases.

Thanks, Nathan.  Let's proceed with the change then.  David, would you
prefer handling the patch you have written by yourself for the query
ID part?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them
Next
From: David Rowley
Date:
Subject: Re: Add comment explaining why queryid is int64 in pg_stat_statements