| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jan Urbański <wulczer(at)wulczer(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: hstores in pl/python |
| Date: | 2010-12-15 14:47:54 |
| Message-ID: | AANLkTi=R4h-kdQFTdjKmEtO2ma0vH=gwZfwT05hqkSYa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 15, 2010 at 9:38 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jan =?utf-8?B?VXJiYcWEc2tp?= <wulczer(at)wulczer(dot)org> writes:
>> OK, here's another master plan:
>
>> 1) hstore_plplython, when loaded, looks for a type called "hstore". If
> you created a "hstore" type that does not come from hstore.so, and you
> still load hstore_plpython, you deserve a segfault.
>
> No, you don't. I said upthread that relying on the name of the type was
> a nonstarter, and it still is. For one thing, this sketch ignores
> search path issues.
Well then we need a reliable way to identify a type. What would satisfy you?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-12-15 14:51:22 | Re: Default mode for shutdown |
| Previous Message | Tom Lane | 2010-12-15 14:47:08 | Re: Default mode for shutdown |