Re: json (b) and null fields

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: json (b) and null fields
Date: 2014-09-29 16:09:31
Message-ID: 26185.1412006971@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Andrew Dunstan (andrew(at)dunslane(dot)net) wrote:
>> That said, doing this as an extension is probably a good way to go,
>> as I suggested upthread, since we could then make it available for
>> 9.4, rather than making people wait until 9.5.

> Two points on this- having it in 9.5 doesn't preclude someone from
> extracting it into an extension for 9.4 (indeed, that makes it far more
> likely for such an extension to actually happen, imv..), and having it
> in core means it's actually generally available and a function which can
> be depended upon, which is far from the case for an extension.

I seem to recall that we've run into practical difficulties with moving
extensions into core. It might be OK for a functions-only extension
though.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2014-09-29 16:11:13 Re: open items for 9.4
Previous Message searcher s 2014-09-29 16:06:10 Full_page_write is off in backup mode