| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: transforms |
| Date: | 2013-03-11 17:11:09 |
| Message-ID: | 20130311171109.GB654@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-03-11 09:55:34 -0700, Josh Berkus wrote:
> On 03/11/2013 09:50 AM, Andres Freund wrote:
> > DO LANGUAGE plperlu $$$$;
> > SELECT NULL::hstore;
>
> Aha, so that's what you meant!
>
> Yeah, it works if I reference both extensions before the CREATE EXTENSION.
>
> In that case, seems like that could be added to the extension SQL, no?
If we don't find a better solution, yes. Why don't we lookup type
input/ouput function for parameters and return type during CREATE
FUNCTION? That should solve the issue in a neater way?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-03-11 17:25:02 | matview patch readability/correctness gripe |
| Previous Message | Tom Lane | 2013-03-11 17:01:12 | Re: postgres_fdw vs data formatting GUCs (was Re: [v9.3] writable foreign tables) |