| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: enhancing plpgsql debug API - returns text value of variable content |
| Date: | 2022-03-17 19:58:10 |
| Message-ID: | CAM-w4HMCqa9e_FFEUNHeQG=m1wmmo1uqNMAjrXn8oNWeB0F1rQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-03-17 20:02:27 | Re: Proposal for internal Numeric to Uint64 conversion function. |
| Previous Message | Greg Stark | 2022-03-17 19:46:34 | Re: Proposal for internal Numeric to Uint64 conversion function. |