From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
Cc: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>, David Steele <david(at)pgmasters(dot)net>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: deparsing utility commands |
Date: | 2015-08-06 15:32:34 |
Message-ID: | 20150806153234.GP2441@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jim Nasby wrote:
> FWIW, my interest in this is largely due to the problems I've had with this
> in the variant type. In particular, using the same resolution rules for
> functions and operators. So I'm wondering if there's a bigger issue here.
I'd be glad to review your variant stuff, but I doubt it's the same
thing at play. Please don't hijack this thread. Deparse is doing some
pretty nasty games with the backend innards to make the deparsed
representation usable generally. We were just missing a simple trick.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2015-08-06 15:33:20 | Re: Freeze avoidance of very large table. |
Previous Message | Alvaro Herrera | 2015-08-06 15:29:15 | Re: Raising our compiler requirements for 9.6 |