Thread

1. pg_stat_activity.query_id <-> pg_stat_statements.queryid

   Daniel Westermann (DWE) <daniel.westermann@dbi-services.com> — 2024-02-15T10:52:42Z

   Hi,
   
   quick question: What would be the cases for a query_id in pg_stat_activity not showing up in pg_stat_statements.queryid assuming pg_stat_statements.max is not yet reached?
   
   Regards
   Daniel
   
   
   

2. Re: pg_stat_activity.query_id <-> pg_stat_statements.queryid

   Julien Rouhaud <rjuju123@gmail.com> — 2024-02-15T15:04:02Z

   Hi,
   
   On Thu, Feb 15, 2024 at 10:52:42AM +0000, Daniel Westermann (DWE) wrote:
   >
   > quick question: What would be the cases for a query_id in pg_stat_activity
   > not showing up in pg_stat_statements.queryid assuming pg_stat_statements.max
   > is not yet reached?
   
   Well, first the query_id in pg_stat_activity is only the query_id of top-level
   statements, that may still be running while pg_stat_statements only show
   statistics of already executed statements (top level only or not depends on
   config).
   
   You may also be running some utility statements, which will display a query_id
   in pg_stat_activity while pg_stat_statements will ignore them by default IIRC.
   
   No other idea apart from that.