Re: hstores in pl/python

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jan Urbański <wulczer(at)wulczer(dot)org>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: hstores in pl/python
Date: 2010-12-14 02:16:43
Message-ID: 13902.1292293003@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Can we arrange to pg_dlopen() the hstore module instead of linking
> against it directly? Seems like that might let you use it when
> available without making it a hard requirement.

That doesn't deal with the issues of (a) what is a reasonable fallback
when the module's not there, and (b) how do you identify which type OID
is really hstore? ("The one named hstore" is the wrong answer.)
Both of these problems are trivial for an in-core datatype, and not at
all trivial if it's an add-on.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2010-12-14 02:21:41 Re: Transaction-scope advisory locks
Previous Message KaiGai Kohei 2010-12-14 02:02:16 Re: rest of works for security providers in v9.1