Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)
Date
Msg-id 198415.1606173197@sss.pgh.pa.us
Whole thread Raw
In response to Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2020-Nov-23, Tom Lane wrote:
>> I'm not too fussed about whether we invent is_log_level_output_client,
>> although that name doesn't seem well-chosen compared to
>> is_log_level_output.

> Just replacing "log" for "client" in that seemed strictly worse, and I
> didn't (don't) have any other ideas.

I never cared that much for "is_log_level_output" either.  Thinking
about renaming it to "should_output_to_log()", and then the new function
would be "should_output_to_client()".

>> Shall I press forward with this, or do you want to?

> Please feel free to go ahead, including the change to ProcSleep.

Will do.

            regards, tom lane



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path
Next
From: Tomas Vondra
Date:
Subject: Re: PoC/WIP: Extended statistics on expressions