| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)trustly(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(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-27 20:53:30 |
| Message-ID: | 553EA1CA.6090601@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/27/15 11:47 AM, Joel Jacobson wrote:
> On Mon, Apr 27, 2015 at 6:14 PM, Marko Tiikkaja <marko(at)joh(dot)to
> <mailto:marko(at)joh(dot)to>> wrote:
>
> That sounds weird. log_min_messages are the messages sent to the
> log; client_min_messages are sent to the client.
> context_min_messages are not sent to a "context", whatever that
> would mean.
>
>
> Good point.
>
> 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?
--
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-27 21:01:13 | Re: Reducing tuple overhead |
| Previous Message | Jim Nasby | 2015-04-27 20:48:58 | Re: Temporal extensions |