Content-Type: multipart/alternative;
 boundary="------------yLT90Z29z79pNMs4k1d0hgeg"
Message-ID: <e3a84833-ccbb-cc1d-a591-267444a92e09@dunslane.net>
Date: Mon, 12 Jun 2023 09:19:08 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.5.0
Content-Language: en-US
To: Tomas Vondra <tomas.vondra@enterprisedb.com>,
 Joel Jacobson <joel@compiler.org>, jian he <jian.universality@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
References: <432e0bf3-5a04-4a0b-8236-ff625008e46b@app.fastmail.com>
 <257197c1-4d28-a8c1-c311-510cbc862e03@enterprisedb.com>
 <9f370c3e-9a1b-4db0-ad93-06f14e7dcc37@app.fastmail.com>
 <44ac4916-5a7b-fd02-e967-4c733ae000fe@enterprisedb.com>
 <d8759507-7db8-4cae-b13e-21ae4e382b89@app.fastmail.com>
 <86073c90-062b-a52a-25cd-fcc3f7a30ed4@enterprisedb.com>
 <0e98dbc4-4116-4e15-bf72-3a7d4ab0d27d@app.fastmail.com>
 <86f8a027-e6d4-65c0-7349-faa3301c8b8b@enterprisedb.com>
 <f5a469c2-ceeb-4631-a133-f0895786d587@app.fastmail.com>
 <CACJufxE=QbDzYYay4Z6MJ=BqdkYiHi_P34YOKduyQ0yyXmMhOw@mail.gmail.com>
 <5ef82fca-6277-4eef-81d6-0d8378e68e6a@app.fastmail.com>
 <9ac829ac-7516-5746-8d50-e9c5e5240956@dunslane.net>
 <bd72309a-176a-765e-5a9e-f132d60db6ff@enterprisedb.com>
 <2040c023-1a52-4366-9716-8c8507bb6e32@app.fastmail.com>
 <0c6099ef-1d10-7375-6775-97f10ce01e3d@enterprisedb.com>
 <f8020997-3b80-4f47-b69e-441eeb715f45@app.fastmail.com>
 <5d8027a7-036f-32c0-a0cc-fe92146b8e5d@enterprisedb.com>
From: Andrew Dunstan <andrew@dunslane.net>
Subject: Re: Do we want a hashset type?
In-Reply-To: <5d8027a7-036f-32c0-a0cc-fe92146b8e5d@enterprisedb.com>
Archived-At: <https://www.postgresql.org/message-id/e3a84833-ccbb-cc1d-a591-267444a92e09%40dunslane.net>
Precedence: bulk

This is a multi-part message in MIME format.
--------------yLT90Z29z79pNMs4k1d0hgeg
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


On 2023-06-12 Mo 09:00, Tomas Vondra wrote:
>
>> What was the json/jsonb story, was it ever an extension before
>> being included in core?
> I don't recall what the exact story was, but I guess the "json" type was
> added to core very long ago (before we started to push back a bit), and
> we added some SQL grammar stuff too, which can't be done from extension.
> So when we added jsonb (much later than json), there wasn't much point
> in not having it in core.
>
>

Not quite.

The json type as added in 9.2 (Sept 2012) and jsonb in 9.4 (Dec 2014). I 
wouldn't call those far apart or very long ago. Neither included any 
grammar changes AFAIR.

But if they had been added as extensions we'd probably be in a whole lot 
more trouble now implementing SQL/JSON, so whether that was foresight or 
laziness I think the we landed on our feet there.


cheers


andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com

--------------yLT90Z29z79pNMs4k1d0hgeg
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 2023-06-12 Mo 09:00, Tomas Vondra
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:5d8027a7-036f-32c0-a0cc-fe92146b8e5d@enterprisedb.com">
      <pre class="moz-quote-pre" wrap="">

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">What was the json/jsonb story, was it ever an extension before
being included in core?
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
I don't recall what the exact story was, but I guess the "json" type was
added to core very long ago (before we started to push back a bit), and
we added some SQL grammar stuff too, which can't be done from extension.
So when we added jsonb (much later than json), there wasn't much point
in not having it in core.


</pre>
    </blockquote>
    <p><br>
    </p>
    <p>Not quite. <br>
    </p>
    <p>The json type as added in 9.2 (Sept 2012) and jsonb in 9.4 (Dec
      2014). I wouldn't call those far apart or very long ago. Neither
      included any grammar changes AFAIR.<br>
    </p>
    <p>But if they had been added as extensions we'd probably be in a
      whole lot more trouble now implementing SQL/JSON, so whether that
      was foresight or laziness I think the we landed on our feet there.<br>
    </p>
    <p><br>
    </p>
    <p>cheers</p>
    <p><br>
    </p>
    <p>andrew<br>
    </p>
    <pre class="moz-signature" signature-switch-id="d0437855-2267-4610-80b3-83167ec45b0b" cols="72">--
Andrew Dunstan
EDB: <a class="moz-txt-link-freetext" href="https://www.enterprisedb.com">https://www.enterprisedb.com</a>
</pre>
  </body>
</html>

--------------yLT90Z29z79pNMs4k1d0hgeg--