From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: patch: function xmltable |
Date: | 2017-01-11 21:53:25 |
Message-ID: | 20170111215325.4zb2arpn3efcl3en@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> The more I look at this, the less I like using NameArgExpr for
> namespaces. It looks all wrong to me, and it causes ugly code all over.
> Maybe I just need to look at it a bit longer.
I think it'd be cleaner to use ResTarget for the namespaces, like
xml_attribute_el does, and split the names from actual exprs in the same
way. So things like ExecInitExpr become simpler because you just
recurse to initialize the list, without having to examine each element
individually. tabexprInitialize can just do forboth().
The main reason I don't like abusing NamedArgExpr is that the whole
comment that explains it becomes a lie.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
xmltable-26.patch | text/plain | 160.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2017-01-11 22:51:42 | Re: CONNECTION LIMIT and Parallel Query don't play well together |
Previous Message | Peter Geoghegan | 2017-01-11 21:53:10 | Re: WIP: [[Parallel] Shared] Hash |