Re: dblink: add polymorphic functions.

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Subject: Re: dblink: add polymorphic functions.
Date: 2016-01-08 15:00:58
Message-ID: 20160108150058.GA583091@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Joe Conway wrote:
> On 07/30/2015 09:51 AM, Tom Lane wrote:
> > Joe Conway <mail(at)joeconway(dot)com> writes:
> >> What about just TYPE then?
> >
> >> SELECT x::TYPE(some_expression) FROM ...
> >> SELECT CAST (x AS TYPE(some_expression)) FROM ...
> > The main limitation of this patch is that it won't work for call sites
> > that pass pstate == NULL to LookupTypeName. There are a fair number
> > of them, some of which wouldn't care because they could never invoke
> > this notation anyway, but for others we'd need to do some work to cons
> > up a suitable pstate.
> Sorry it took so long for me to get back to this, but any reason the
> attached won't work?

So, is this going anywhere?

Álvaro Herrera
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-01-08 15:01:26 Re: pgsql: Blind attempt at a Cygwin fix
Previous Message Alvaro Herrera 2016-01-08 14:49:51 pgsql: Blind attempt at a Cygwin fix