Re: Improve error handling in pltcl - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Improve error handling in pltcl
Date
Msg-id 56F20E12.2040102@BlueTreble.com
Whole thread Raw
In response to Re: Improve error handling in pltcl  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On 3/20/16 8:42 PM, Jim Nasby wrote:
>> The doc example also makes me think that more effort should get expended
>> on converting internalquery/internalpos to just be query/cursorpos.
>> It seems unlikely to me that a Tcl function could ever see a case
>> where the latter fields are useful directly.
>
> Is there docs or an example on how to handle that? I looked at the
> plpython stuff and I'm still really unclear on what exactly an
> internalquery is as opposed to regular context info?
> PLy_spi_exception_set simply exposes the raw internalquery and internalpos.

Anyone any pointers on this? I'm not sure I can finish the docs without 
knowing what we want to do here.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Speed up Clog Access by increasing CLOG buffers
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Show dropped users' backends in pg_stat_activity