| From: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
|---|---|
| To: | "Peter Eisentraut" <peter(dot)eisentraut(at)enterprisedb(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Add result_types column to pg_prepared_statements view |
| Date: | 2022-07-05 07:31:27 |
| Message-ID: | dd516b54-76b8-40ab-a39f-16c64571e537@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 5 Jul 2022, at 06:34, Peter Eisentraut wrote:
> On 01.07.22 14:27, Dagfinn Ilmari Mannsåker wrote:
>> Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
>>
>>> On 19.05.22 17:34, Dagfinn Ilmari Mannsåker wrote:
>>>> Prompted by a question on IRC, here's a patch to add a result_types
>>>> column to the pg_prepared_statements view, so that one can see the types
>>>> of the columns returned by a prepared statement, not just the parameter
>>>> types.
>>>> I'm not quite sure about the column name, suggestions welcome.
>>>
>>> I think this patch is sensible.
>
>> The arguments about client-side type-specific value handling for
>> RowDescription don't apply here IMO, since this view is more
>> user-facing.
>
> I agree. It's also easy to change if needed. Committed as is.
Thanks!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2022-07-05 07:33:17 | Re: [PoC] Improve dead tuple storage for lazy vacuum |
| Previous Message | Michael Paquier | 2022-07-05 07:22:19 | Re: [PATCH] Completed unaccent dictionary with many missing characters |