Re: Problems around compute_query_id

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Michael Banck <michael(dot)banck(at)credativ(dot)de>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: Problems around compute_query_id
Date: 2021-04-12 07:26:33
Message-ID: 20210412072633.hdztcscmvcbq6nj2@nol
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 12, 2021 at 09:20:07AM +0200, Michael Banck wrote:
>
> What about log_statement_sample_rate ? Does compute_query_id have the
> same problem with that?

No, log_statement_sample_rate samples log_min_duration_statements, not
log_statements so it works as expected.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2021-04-12 07:42:50 Re: ALTER TABLE .. DETACH PARTITION CONCURRENTLY
Previous Message Michael Banck 2021-04-12 07:20:07 Re: Problems around compute_query_id