Re: pg_prepared_statements missing column
От | Julien Rouhaud |
---|---|
Тема | Re: pg_prepared_statements missing column |
Дата | |
Msg-id | 20221113125456.haj43yqczgodiak3@jrouhaud обсуждение исходный текст |
Ответ на | pg_prepared_statements missing column (Peter Gigowski <gigawowski@gmail.com>) |
Ответы |
Re: pg_prepared_statements missing column
|
Список | pgsql-bugs |
Hi, On Sat, Nov 12, 2022 at 11:37:34PM -0800, Peter Gigowski wrote: > > My buddy and I were running through the 15.1 docs today and found the > pg_prepared_statements view doesn't include the return_type column like it > says it should. > > Here is the printout from /d pg_prepared_statements > View "pg_catalog.pg_prepared_statements" Column | Type | Collation | > Nullable | Default > -----------------+--------------------------+-----------+----------+--------- > name | text | | | statement | text | | | prepare_time | timestamp with time > zone | | | parameter_types | regtype[] | | | from_sql | boolean | | | > generic_plans | bigint | | | custom_plans | bigint | | | > > My version: > PostgreSQL 15.1 (Debian 15.1-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled > by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit > > Link to docs: > https://www.postgresql.org/docs/15/view-pg-prepared-statements.html > > I'm not sure exactly what to make of it, but I wanted to submit a ticket. Indeed! It's a documentation bug. This was apparently an oversight when packpatching 5766443695d (Bruce in Cc), as it introduced the result_types column in the documentation in pg15 while the feature itself is only introduced in pg16 (84ad713cf85).
В списке pgsql-bugs по дате отправления: