Re: Typmod associated with multi-row VALUES constructs
| От | Pavel Stehule |
|---|---|
| Тема | Re: Typmod associated with multi-row VALUES constructs |
| Дата | |
| Msg-id | CAFj8pRCqKmXUMeLsbhqGJMq7U5Fb6woq2gtJFTgSOApciFodRw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Typmod associated with multi-row VALUES constructs (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Список | pgsql-hackers |
2016-12-07 22:17 GMT+01:00 Alvaro Herrera <alvherre@2ndquadrant.com>:
Tom Lane wrote:
> In HEAD, we could change the RTE data structure so that
> transformValuesClause could save the typmod information in the RTE,
> keeping the lookups cheap.
Hmm, I think this would be useful for the XMLTABLE patch too. I talked
a bit about it at
https://www.postgresql.org/message-id/20161122204730. dgipy6gxi25j4e6a@alvherre. pgsql
The patch has evolved quite a bit since then, but the tupdesc continues
to be a problem. Latest patch is at
https://www.postgresql.org/message-id/CAFj8pRBsrhwR636-_ 3TPbqu%3DFo3_DDer6_yp_ afzR7qzhW1T6Q%40mail.gmail.com
What do you dislike on tupdesc usage there?
regards
Pavel
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: