| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org>, Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, Jim Mlodgenski <jimmy76(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
| Subject: | Re: [v9.5] Custom Plan API |
| Date: | 2014-05-09 02:43:57 |
| Message-ID: | 20140509024357.GJ2556@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Kouhei Kaigai (kaigai(at)ak(dot)jp(dot)nec(dot)com) wrote:
> > So the extension will need to be aware of all custom data types and then
> > installed *after* all other extensions are installed? That doesn't strike
> > me as workable...
> >
> I'm not certain why do you think an extension will need to support all
> the data types.
Mostly because we have a very nice extension system which quite a few
different extensions make use of and it'd be pretty darn unfortunate if
none of them could take advtange of GPUs because we decided that the
right way to support GPUs was through an extension.
This is argument which might be familiar to some as it was part of the
reason that json and jsonb were added to core, imv...
> Even if it works only for a particular set of data types, it makes sense
> as long as it covers data types user actually using.
I know quite a few users of PostGIS, ip4r, and hstore...
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-05-09 02:46:57 | Re: [v9.5] Custom Plan API |
| Previous Message | Peter Geoghegan | 2014-05-09 02:39:23 | Re: [v9.5] Custom Plan API |