MIME-Version: 1.0
References: <CAKU4AWoqAVya6PBhn+BCbFaBMt3z-2=i5fKO3bW=6HPhbid2Dw@mail.gmail.com>
 <CACJufxHASOEpngQ8V2tbXgs4VZC3ETrVbS=uk0KC_B_J1j7ejQ@mail.gmail.com>
 <CAKU4AWrap1zpYqunJwWTN=CdP7E8e0U4mYmwn7hvTW3ERuENVg@mail.gmail.com>
 <CAFj8pRD-R-GsGCjeYApbhZoiW8TV6zACaYStMBMM0=--+WgN_A@mail.gmail.com>
 <CAKU4AWpDdFXAD+dMC1HeErXSKBUUBRGWkf=dAcX3wZgBNsWM=g@mail.gmail.com>
 <CAFj8pRAO3oEiBaJJ9=HZp6CoP2ffbwSgrKkLKjPfYZwx9wOOuQ@mail.gmail.com>
 <CAKU4AWoCHpKAVuQeOrk44cVPy_dVxn1aHrMUvHy5Ag-daFCSsQ@mail.gmail.com>
 <CAFj8pRD4cdUmK0RG4oN5B2KRSeDhwfMYaL=XpfEu4iaLeZ_Kow@mail.gmail.com>
 <CAKU4AWp8ab61e96v57OaB-Gm1bMfBNVLVy+s17U6_Ne3veB84g@mail.gmail.com> <3507485.1691090027@sss.pgh.pa.us>
In-Reply-To: <3507485.1691090027@sss.pgh.pa.us>
From: Andy Fan <zhihui.fan1213@gmail.com>
Date: Fri, 4 Aug 2023 12:38:23 +0800
Message-ID: <CAKU4AWoLfjLi+maMxHxjL0OwSPcs58yiSgz-OiRodVpB5CvD1w@mail.gmail.com>
Subject: Re: Extract numeric filed in JSONB more effectively
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, jian he <jian.universality@gmail.com>, 
	pgsql-hackers <pgsql-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000035179c06021178cd"
Archived-At: <https://www.postgresql.org/message-id/CAKU4AWoLfjLi%2BmaMxHxjL0OwSPcs58yiSgz-OiRodVpB5CvD1w%40mail.gmail.com>
Precedence: bulk

--00000000000035179c06021178cd
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Tom:

On Fri, Aug 4, 2023 at 3:13=E2=80=AFAM Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Andy Fan <zhihui.fan1213@gmail.com> writes:
> >> If you use explicit cast, then the code should not be hard, in the
> >> rewrite stage all information should be known.
>
> > Can you point to me where the code is for the XML stuff?
>
> I think Pavel means XMLTABLE, which IMO is an ugly monstrosity of
> syntax --- but count on the SQL committee to do it that way :-(.
>

Thanks for this input!


>
> As far as the current discussion goes, I'm strongly against
> introducing new functions or operators to do the same things that
> we already have perfectly good syntax for.  "There's more than one
> way to do it" isn't necessarily a virtue, and for sure it isn't a
> virtue if people have to rewrite their existing queries to make use
> of your optimization.
>

I agree, this is always the best/only reason I'd like to accept.


>
>
> I do like the idea of attaching a Simplify planner support function
> to jsonb_numeric (and any other ones that seem worth optimizing)
>

I have a study planner support function today,  that looks great and
I don't think we need much work to do to get our goal, that's amzing.

For all the people who are interested in this topic, I will post a
planner support function soon,  you can check that then.

--=20
Best Regards
Andy Fan

--00000000000035179c06021178cd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Tom:</div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Fri, Aug 4, 2023 at 3:13=E2=80=AFAM Tom La=
ne &lt;<a href=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Andy Fan &lt;<=
a href=3D"mailto:zhihui.fan1213@gmail.com" target=3D"_blank">zhihui.fan1213=
@gmail.com</a>&gt; writes:<br>
&gt;&gt; If you use explicit cast, then the code should not be hard, in the=
<br>
&gt;&gt; rewrite stage all information should be known.<br>
<br>
&gt; Can you point to me where the code is for the XML stuff?<br>
<br>
I think Pavel means XMLTABLE, which IMO is an ugly monstrosity of<br>
syntax --- but count on the SQL committee to do it that way :-(.<br></block=
quote><div><br></div><div>Thanks for this input!=C2=A0</div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
As far as the current discussion goes, I&#39;m strongly against<br>
introducing new functions or operators to do the same things that<br>
we already have perfectly good syntax for.=C2=A0 &quot;There&#39;s more tha=
n one<br>
way to do it&quot; isn&#39;t necessarily a virtue, and for sure it isn&#39;=
t a<br>
virtue if people have to rewrite their existing queries to make use<br>
of your optimization.<br></blockquote><div><br></div><div>I agree, this is =
always the best/only reason I&#39;d like to accept.=C2=A0</div><div>=C2=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
I do like the idea of attaching a Simplify planner support function<br>
to jsonb_numeric (and any other ones that seem worth optimizing)<br></block=
quote><div>=C2=A0</div><div>I have a study planner support function today,=
=C2=A0 that looks great and</div><div>I don&#39;t think we need much work t=
o do to get our goal, that&#39;s amzing.</div><div><br></div><div>For all t=
he people who are interested in this topic, I will post a=C2=A0</div><div>p=
lanner support function soon,=C2=A0 you can check that then.</div></div><di=
v><br></div><span class=3D"gmail_signature_prefix">-- </span><br><div dir=
=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Best Regards<div>Andy F=
an</div></div></div></div>

--00000000000035179c06021178cd--