| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, 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 05:34:24 |
| Message-ID: | 5a1f587b-0d89-3ade-ea7e-4878e1d3e144@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-07-05 05:36:24 | Re: AIX support - alignment issues |
| Previous Message | Andres Freund | 2022-07-05 05:31:50 | Re: AIX support - alignment issues |