From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
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 22:02:55 |
Message-ID: | 166823.1606168975@sss.pgh.pa.us |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Well, we already do this in a number of places. But I can get behind
> this:
>> Maybe it'd be a good idea to have elog.c expose a new function
>> along the lines of "bool message_level_is_interesting(int elevel)"
>> to support this and similar future optimizations in a less fragile way.
I'll see about a patch for that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Anastasia Lubennikova | 2020-11-23 22:08:35 | Re: New default role- 'pg_read_all_data' |
Previous Message | Tom Lane | 2020-11-23 22:00:41 | Re: optimizer/clauses.h needn't include access/htup.h |