Re: proposal: enhancing plpgsql debug API - returns text value of variable content - Mailing list pgsql-hackers

From Greg Stark
Subject Re: proposal: enhancing plpgsql debug API - returns text value of variable content
Date
Msg-id CAM-w4HMCqa9e_FFEUNHeQG=m1wmmo1uqNMAjrXn8oNWeB0F1rQ@mail.gmail.com
Whole thread Raw
In response to Re: proposal: enhancing plpgsql debug API - returns text value of variable content  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: enhancing plpgsql debug API - returns text value of variable content  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: proposal: enhancing plpgsql debug API - returns text value of variable content  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
It looks like this is -- like a lot of plpgsql patches -- having
difficulty catching the attention of reviewers and committers.
Aleksander asked for a test and Pavel put quite a bit of work into
adding a good test case. I actually like that there's a test because
it shows the API can be used effectively.

From my quick skim of this code it does indeed look like it's ready to
commit. It's mostly pretty mechanical code to expose a couple fields
so that a debugger can see them.

Pavel, are you planning to add a debugger to contrib using this? The
test example code looks like it would already be kind of useful even
in this form.



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Proposal for internal Numeric to Uint64 conversion function.
Next
From: Tom Lane
Date:
Subject: Re: Proposal for internal Numeric to Uint64 conversion function.