| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, James Coleman <jtc331(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait) |
| Date: | 2020-11-23 23:02:07 |
| Message-ID: | 20201123230207.GA2935@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Nov-23, Tom Lane wrote:
> Ah, I see I didn't cover the case in ProcSleep that you were originally on
> about ... I'd just looked for existing references to log_min_messages
> and client_min_messages.
Yeah, it seemed bad form to add that when you had just argued against it
:-)
> I think it's important to have the explicit check for elevel >= ERROR.
> 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.
> Shall I press forward with this, or do you want to?
Please feel free to go ahead, including the change to ProcSleep.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-11-23 23:06:19 | Re: pg_ls_tmpdir to show directories and shared filesets (and pg_ls_*) |
| Previous Message | Stephen Frost | 2020-11-23 23:00:31 | Re: pg_ls_tmpdir to show directories and shared filesets (and pg_ls_*) |