Request a Demo
Home   >   mailing lists

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

From Sami Imseih
Subject Re: Add comment explaining why queryid is int64 in pg_stat_statements
Date
Msg-id CAA5RZ0ux+634SbsrJo3qjFKv-PfKxi4UTeQ3Me4xZVERrfURnA@mail.gmail.com
Whole thread Raw
In response to Re: Add comment explaining why queryid is int64 in pg_stat_statements  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
Tree view 
FWIW, all the hash function SQL interfaces, \df hash*,
have this behavior in which the result is a signed (int/bigint),
but the internal representation of the hash is an unsigned (int/bigint).

I am not sure why a comment is needed specifically for pg_stat_statements


--
Sami Imseih
Amazon Web Services (AWS)

pgsql-hackers by date:

Previous
From: Jose Luis Tallon
Date:
Subject: Re: Violation of principle that plan trees are read-only
Next
From: Nathan Bossart
Date:
Subject: Re: Remove Instruction Synchronization Barrier in spin_delay() for ARM64 architecture