Re: json (b) and null fields - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: json (b) and null fields
Date
Msg-id CAHyXU0zqMHtN12CYn9rbgdPkpd3BXe+iEQw4Fzqa_nW2r6Bong@mail.gmail.com
Whole thread Raw
In response to Re: json (b) and null fields  (Stephen Frost <sfrost@snowman.net>)
Responses Re: json (b) and null fields
List pgsql-hackers
On Mon, Sep 29, 2014 at 9:45 AM, Stephen Frost <sfrost@snowman.net> wrote:
> * Robert Haas (robertmhaas@gmail.com) wrote:
>> +1.  I am sort of surprised that anyone things this null-stripping
>> behavior is something that ought to be part of core PostgreSQL instead
>> of, I don't know, relegated to an extension somewhere far from the
>> bright center of the galaxy.  I've never heard of that requirement
>> anywhere but here.  But if other people feel we should have it, that's
>> fine - but certainly making it a separate function makes a lot more
>> sense.
>
> I'm not at all surprised by the request, and I do believe it to be
> worthwhile to have in core as it's a pretty common pattern with JSON.
> That said, making it part of an operator function wasn't the right
> approach and it should be an independent function.

Are you defining 'core' as 'supported by the core project' (in which
case I agree) or 'not an extension' (in which case I disagree).

merlin



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [REVIEW] Re: Compression of full-page-writes
Next
From: Andres Freund
Date:
Subject: Re: [REVIEW] Re: Compression of full-page-writes