On Feb 27, 2014, at 11:15 PM, Peter Geoghegan <p...@heroku.com> wrote:
> I don't think that's obvious at all. Anyone is free to spend their > time however they please, but personally I don't think that that's a > wise use of anyone's time. I believe you are misunderstanding me. If there are actual technical problems or snags to migrating jsonb into core with full operator and index support, then the way we find out is to do the implementation, unless you know of a specific technical holdup already. > There are no technical issues of any real consequence in this specific > instance. There was no technical reason that json couldn't have been an extension, either, but there were very compelling presentational reasons to have it in core. jsonb has exactly the same presentational issues. > Yes, people who have the ability to block the feature entirely. I am > attempting to build consensus by reaching a compromise that weighs > everyone's concerns. The thing I still haven't heard is why jsonb in core is a bad idea, except that it is too much code. Is that the objection? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
