Re: Include a timestamp in future versions of pg_stat_statements when when a query entered the cache?

Hi, On Tue, Dec 05, 2023 at 06:28:54AM -0800, Jerry Brenner wrote: > It would be helpful if a timestamp column was added to pg_stat_statements > to denote when a query entered the view. This would make it easier to tell > how frequently a query is being executed (100,000 times since a specific >

Include a timestamp in future versions of pg_stat_statements when when a query entered the cache?

It would be helpful if a timestamp column was added to pg_stat_statements to denote when a query entered the view. This would make it easier to tell how frequently a query is being executed (100,000 times since a specific timestamp vs 100,000 times since the execution stats were last reset.) I re

Re: Does Postgres have consistent identifiers (plan hash value) for explain plans?

Apologies if I'm not using the appropriate Postgres-specific terms. The simplest implementation would consider only the information that is consistent across systems and executions - node types, relation and index names (not ids), aliases ... It would ignore bind variable values and execution sta