| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Call stacks and RAISE INFO |
| Date: | 2011-10-15 15:13:56 |
| Message-ID: | 12475.1318691636@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> 2011/10/15 Robert Haas <robertmhaas(at)gmail(dot)com>:
>> On Sat, Oct 15, 2011 at 12:24 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>> I have no problem with this. A context can be false for info and true
>>> for other in default. Please, use a different identifier than
>>> "context", that can be use for reading context in future - maybe
>>> "attach_context" or some similar.
>> error_context?
> what about show_context, hide_context, hold_context, use_context ??
I still think it should be CONTEXT, period. All the other options to
RAISE are named directly after the message lines they control; why
should this one be different?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-10-15 15:23:37 | Re: pg_dump vs malloc |
| Previous Message | Alexander Korotkov | 2011-10-15 15:13:51 | Re: WIP: collect frequency statistics for arrays |