Re: PL/pgSQL, RAISE and error context
| От | Pavel Stehule |
|---|---|
| Тема | Re: PL/pgSQL, RAISE and error context |
| Дата | |
| Msg-id | CAFj8pRAY-H8H1R69ZR_2Q_foPabokc7JyY4xKuN-c9cjVK9Y5Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: PL/pgSQL, RAISE and error context (Merlin Moncure <mmoncure@gmail.com>) |
| Ответы |
Re: PL/pgSQL, RAISE and error context
|
| Список | pgsql-hackers |
2015-07-21 16:58 GMT+02:00 Merlin Moncure <mmoncure@gmail.com>:
On Tue, Jul 21, 2015 at 2:53 AM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> On 07/21/2015 10:38 AM, Pavel Stehule wrote:
>>
>> where we are with this patch? Can I do some for it?
>
>
> I still feel this approach is misguided, and we should be tweaking psql
> and/or libpq instead. I don't feel strongly though, and if some other
> committer wants to pick this up in its current form, I won't object. So this
> patch has reached an impasse, and if no-one else wants to pick this up, I'm
> going to mark this as "Returned with Feedback" and move on.
That's unfortunate. Maybe I'm missing something:
What does a client side implementation offer that a server side
implementation does not offer?
I have not any problem to change the filtering to client side. Primary question is fix of PLpgSQL RAISE statement issue - The context field filtering is a necessary follow-up and trivial in both cases.
In this case, it is acceptable for all?
Regards
Pavel
merlin
В списке pgsql-hackers по дате отправления: