From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Joel Jacobson <joel(at)trustly(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
Subject: | Re: PL/pgSQL, RAISE and error context |
Date: | 2015-04-28 17:44:44 |
Message-ID: | 553FC70C.2070109@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/28/15 1:16 AM, Pavel Stehule wrote:
>
> I think it can't be any clearer than the proposed
> "plpgsql.display_context_min_messages"
>
>
> client_min_context. It's doing the same thing as min_messages does,
> just for context instead of the message.
>
> Or does this affect client and log the same way?
>
>
> it affect client and log together
>
> maybe "min_context"
+1
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2015-04-28 17:48:33 | Re: Fwd: [GENERAL] 4B row limit for CLOB tables |
Previous Message | Jim Nasby | 2015-04-28 17:44:04 | Re: Allow SQL/plpgsql functions to accept record |