From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Remaining 'needs review' patchs in July commitfest |
Date: | 2015-07-30 18:47:09 |
Message-ID: | CA+TgmoafKJc3p1jgYmqq-j1NuSb--ONfZi7o52ptv84gLYFSQw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 29, 2015 at 5:08 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Tue, Jul 28, 2015 at 3:51 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>>>> plpgsql raise statement with context
>>> Impasse. Everyone wants this feature in some form, but no consensus on
>>> whether to do this client-side or server-side.
>
>> +1 for server-side. Does anyone other than you even think that the
>> client side is a reasonable way to go?
>
> Yes. This is presupposing on the server side what the client will want
> to display.
Fair enough. I'm still not convinced we're doing anything other than
complicating what ought to be a simple matter. It is just a fact that
logging tracing messages in PL/pgsql functions is a pain in the butt
right now in some situations because you get a huge number of CONTEXT
lines that you don't want. Can we agree on some solution to that
problem without over-engineering this to infinity?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-07-30 20:01:40 | Re: brin index vacuum versus transaction snapshots |
Previous Message | Robert Haas | 2015-07-30 18:32:44 | Re: Reduce ProcArrayLock contention |