| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL, RAISE and error context |
| Date: | 2015-04-23 13:55:19 |
| Message-ID: | CAFj8pRB-WqzU=agj3_7=GohBm_zgee7ekgem=oJJNoYrUwmD0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2015-04-23 15:47 GMT+02:00 Robert Haas <robertmhaas(at)gmail(dot)com>:
> On Thu, Apr 23, 2015 at 4:56 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
> > I don't see a contradiction. There is clean agreement, so ERROR level
> should
> > to show the context. NOTICE and WARNINGs doesn't need it - and there is a
> > backward compatibility and usability reasons don't do it.
>
> Whether notices and warnings need it is a matter of opinion. I don't
> think your idea is bad, and it might be a good rule of thumb in many
> cases, but I slightly prefer Marko's approach of adding a new option.
>
I am not sure if I understand to you.
please, can you write more about your idea?
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2015-04-23 14:00:54 | Re: Code paths where LWLock should be released on failure |
| Previous Message | Andres Freund | 2015-04-23 13:50:24 | Re: INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0 |