Re: Syntax error reporting (was Re: [PATCHES] syntax error

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Syntax error reporting (was Re: [PATCHES] syntax error
Date: 2004-03-22 16:35:29
Message-ID: Pine.LNX.4.58.0403221729030.7217@sablons.cri.ensmp.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


> > Maybe I missed something, but it seemed to me that strings are appended
> > on to the other, and there is no way back.
>
> But the string list is not constructed until the error actually occurs.
> You don't need a pop at that point --- the call stack is what it is.
>
> I think you are imagining that outer-level context hooks should be able
> to editorialize on what inner-level ones said (or perhaps vice versa?)

No.

I just missed the "error_context_stack" by focussing on "errcontext()",
which does not managed a stack at all, so I was quite puzzled. Now
it is clearer.

Thanks,

--
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2004-03-22 17:14:59 Re: [PATCHES] UnixWare/CVS Tip/initdb.c needs to use
Previous Message Matthew T. O'Connor 2004-03-22 16:22:20 Re: pg_autovacuum next steps

Browse pgsql-patches by date

  From Date Subject
Next Message Larry Rosenman 2004-03-22 17:14:59 Re: [PATCHES] UnixWare/CVS Tip/initdb.c needs to use
Previous Message Tom Lane 2004-03-22 15:12:01 Re: Syntax error reporting (was Re: [PATCHES] syntax error position "CREATE FUNCTION" bug fix)