Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qoIEf-000m1B-C0 for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Oct 2023 06:53:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qoIEd-009hbF-50 for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Oct 2023 06:53:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qoIEc-009hXz-QT for pgsql-hackers@lists.postgresql.org; Thu, 05 Oct 2023 06:53:23 +0000 Received: from mail-oo1-xc2f.google.com ([2607:f8b0:4864:20::c2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qoIEZ-0007x8-3M for pgsql-hackers@postgresql.org; Thu, 05 Oct 2023 06:53:21 +0000 Received: by mail-oo1-xc2f.google.com with SMTP id 006d021491bc7-57b64731334so364934eaf.1 for ; Wed, 04 Oct 2023 23:53:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696488796; x=1697093596; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7pOT4FyFfgfvER0bp2Qm/BOcsCef5EdrlZuFY+gEDnM=; b=GswAWYgMRmACRI0cVgy8MXZbfhLT/xcdl9YI8ARouCgld3rwWLJbKhVDgxyDjUHp6h Zykbjpprcx7P1OCssayLdG12m4QxX8D/FGorgLV/49LZBZEkDg4ko71TCesvZgvPe7du KCmJyYHcLG1VY4qi22zYJdJlWaNtLxrTjF+sUSzoQRmMPhjH1YniGYMmx+dCoEMPiLxQ KtM+TwK1nhVjWobcb39kYR141LxYJ/KxUi3BZUV5X3AKxxsO9Lo1QwN9L3YeJRYJZea/ vYhyZ9De5gKS6QLJ/K1iQYlu6EO5E5znAYxSByvLQ9HvfQrjKFu7wOPTpCJB0FjTBzJg Aslg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696488796; x=1697093596; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7pOT4FyFfgfvER0bp2Qm/BOcsCef5EdrlZuFY+gEDnM=; b=EdSikGaIqZ7wwGSyaVOtao27doSABkanbG9fPcIAAIxtZe0faAl2YhEoPRLli/0muh zxqsy60LV73X8Te4gRYrcO8pimeR5jgyCUGHEKH5DpyQmdPd/r904ljWF5r0MyJ/zBUZ DAp4S/6WC8T5/JchF3DDSVH6ivTa2O4uy0T7+/41VqxumQgUrgFRlLbdIihxriK8CIS/ Rpg/1l2J2ZlvZ4DgZfynnCVsZ3wINFwVDdB0yG4Yu1K0x3v/qXFXC1O0j770Hk0Nrhw5 Z367YfDkcJjeQncVVsloNm5Bpevzfo5zoLDPPWESbSDHUaTq8vPENJAeKSkOgkUdyv6w epiw== X-Gm-Message-State: AOJu0Ywm+yXyTqOHFP7c8FR08S0DVsGH6kFNp2ueru5LFdILQXej/2CZ lwijU81roK7u2Tg8etMDKKE0hlEdUvuLnpJdE2E= X-Google-Smtp-Source: AGHT+IH/EzhGXObiM0nweBMCd/LCsisXq3B3J6rk01yA5GGqbSRwexGi2Djd3zR1N01+xjweHbqpVNtYcQ5eMwaRLBg= X-Received: by 2002:a4a:8081:0:b0:57b:6a40:8a9e with SMTP id z1-20020a4a8081000000b0057b6a408a9emr3869747oof.7.1696488796564; Wed, 04 Oct 2023 23:53:16 -0700 (PDT) MIME-Version: 1.0 References: <3507485.1691090027@sss.pgh.pa.us> <900892914fdc3f477b101d699efb40e0@anastigmatix.net> <903341.1692022214@sss.pgh.pa.us> <4b97f1a1dd9b6e45443d24870d3be698@anastigmatix.net> <111272f2dc112c7becdd35ad89f6b935@anastigmatix.net> <5138c6b5fd239e7ce4e1a4e63826ac27@anastigmatix.net> <369543439e988ae43f0a6307500b27c4@anastigmatix.net> <5955e93347a7e3b1612cf7e129ae6d04@anastigmatix.net> <43a988594ac91a63dc4bb49a94303a42@anastigmatix.net> In-Reply-To: From: Andy Fan Date: Thu, 5 Oct 2023 14:53:05 +0800 Message-ID: Subject: Re: Extract numeric filed in JSONB more effectively To: Chapman Flack Cc: jian he , Pavel Stehule , Tom Lane , pgsql-hackers Content-Type: multipart/alternative; boundary="00000000000015b3440606f29454" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000015b3440606f29454 Content-Type: text/plain; charset="UTF-8" Hi, I am feeling this topic has been well discussed and the only pending issues are below, it would be great that any committer can have a look at these, so I mark this entry as "Ready for Committer". Things are not addressed yet: > 1. the error message handling. > You can check [1] for more background of this, I think blocking this feature at an error message level is not pretty reasonable. > 2. if we have chances to optimize _tz functions, I guess no. > patch 002 is dedicated for this, I think it should not be committed, the reason is described in the commit message. 3. function naming issue. I think I can get it modified once after > all the other issues are addressed. > > [1] https://www.postgresql.org/message-id/d70280648894e56f9f0d12c75090c3d8%40anastigmatix.net -- Best Regards Andy Fan --00000000000015b3440606f29454 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I am feeling this topic has been well discussed=C2=A0and the only pe= nding=C2=A0
issues are below,=C2=A0 it would be great that any co= mmitter can have a=C2=A0
look at these,=C2=A0 so I mark this entr= y as "Ready for Committer".=C2=A0

Thi= ngs are not addressed yet:
1.=C2=A0 the error message handling.= =C2=A0

You can check [1] for mo= re background of this,=C2=A0 I think blocking this
feature at an = error message level is not pretty reasonable.=C2=A0
=C2=A0
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">
2.= =C2=A0 if we have chances to optimize _tz functions, I guess no.
=C2=A0
patch 002 is dedicated=C2=A0 for this,= =C2=A0 I think it should not be committed,
the reason is describe= d in the commit message.

3.=C2=A0 function naming issue. I= think I can get it modified once after
all the other issues are = addressed.=C2=A0

-- =
Best Regard= s
Andy Fan
--00000000000015b3440606f29454--