From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Notice lock waits |
Date: | 2016-08-10 00:17:14 |
Message-ID: | 94057884-e9c6-6b40-2dbb-7b6d67e5de61@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/5/16 12:00 PM, Jeff Janes wrote:
> So I created a new guc, notice_lock_waits, which acts like
> log_lock_waits but sends the message as NOTICE so it will show up on
> interactive connections like psql.
I would strongly prefer that this accept a log level instead of being
hard-coded to NOTICE. The reason is that I find the NOTICE chatter from
many DDL commands to be completely worthless (looking at you %TYPE), so
I normally set client_min_messages to WARNING in DDL scripts. I can work
on that patch; would it essentially be a matter of changing
notice_lock_waits to int lock_wait_level?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2016-08-10 02:07:41 | Re: Heap WARM Tuples - Design Draft |
Previous Message | Claudio Freire | 2016-08-09 23:46:21 | Re: Heap WARM Tuples - Design Draft |