Re: Generating code for query jumbling through

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>
Subject: Re: Generating code for query jumbling through
Date: 2023-01-28 03:32:21
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Jan 24, 2023 at 03:57:56PM +0900, Michael Paquier wrote:
> Still, my plan here is to enforce the loading of
> pg_stat_statements with compute_query_id = regress and
> utility_query_id = jumble (if needed) in a new buildfarm machine,

Actually, about this specific point, I have been able to set up a
buildfarm machine that uses shared_preload_libraries =
pg_stat_statements and compute_query_id = regress in the base
configuration, which is uncovered yet. This works as long as one sets
up EXTRA_INSTALL => "contrib/pg_stat_statements" in build_env.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2023-01-28 03:34:27 Re: heapgettup refactoring
Previous Message Andres Freund 2023-01-28 03:07:51 Re: Something is wrong with wal_compression