Re: jsonb and nested hstore - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: jsonb and nested hstore
Date
Msg-id 5317454C.4020601@dunslane.net
Whole thread Raw
In response to Re: jsonb and nested hstore  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: jsonb and nested hstore  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 03/05/2014 10:30 AM, Tom Lane wrote:
> Merlin Moncure <mmoncure@gmail.com> writes:
>> On Wed, Mar 5, 2014 at 9:24 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Also, there might be other cases besides arrays where we've embedded
>>> type OIDs in on-disk data; anyone remember?
>> composite types.
> But that's only the composite type's own OID, no?  So it's not really
> a problem unless the type we wanted to move into (or out of) core was
> itself composite.
>
>             


Sure, although that's not entirely impossible to imagine. I admit it 
seems less likely, and I could accept it as a restriction if we 
conquered the general case.

cheers

andrew



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: jsonb and nested hstore
Next
From: Bruce Momjian
Date:
Subject: Re: jsonb and nested hstore