| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Badly designed error reporting code in controldata_utils.c |
| Date: | 2016-03-08 04:51:01 |
| Message-ID: | 20160308045101.zsskmonxnmjip2un@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-03-08 13:45:25 +0900, Michael Paquier wrote:
> On Mon, Mar 7, 2016 at 10:26 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > FWIW I'm considering implementing elog/ereport properly for the
> > frontend. We've grown several hacks around that not being present, and
> > I think those by now have a higher aggregate complexity than a proper
> > implementation would have.
>
> That would be handy. And this is are going to need something like
> callbacks to allow frontend applications how to apply elevel. Take for
> example pg_rewind, it has an interface with DEBUG and PROGRESS level
> directly embedded with FATAL controlled by user-defined options.
What does "directly embedded with FATAL" mean?
I don't really want to go further than what our system already is
capable of; once we have that we can look for the next steps.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-03-08 05:23:28 | Re: Badly designed error reporting code in controldata_utils.c |
| Previous Message | Michael Paquier | 2016-03-08 04:45:25 | Re: Badly designed error reporting code in controldata_utils.c |