Re: SQL/JSON revisited

Amit Langote <amitlangote09@gmail.com>

From: Amit Langote <amitlangote09@gmail.com>
To: vignesh C <vignesh21@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>, Andrew Dunstan <andrew@dunslane.net>, e.indrupskaya@postgrespro.ru
Date: 2023-01-30T06:39:12Z
Lists: pgsql-hackers

Attachments

On Fri, Jan 27, 2023 at 11:27 PM vignesh C <vignesh21@gmail.com> wrote:
> On Tue, 17 Jan 2023 at 19:01, Amit Langote <amitlangote09@gmail.com> wrote:
> > And I've just finished doing that.  In the attached updated 0004,
> > which adds the JsonExpr node, its evaluation code is now broken into
> > ExprEvalSteps to handle the subsidiary JsonCoercion and JsonBehavior
> > expression nodes that previously used ExprState for recursive
> > evaluation.  Andres didn't like the latter as previously discussed at
> > [1].
> >
> > I've also attached the patch that Elena has proposed as the patch
> > 0011.  I haven't managed to review it yet, though once I do, I'll
> > merge it into the main documentation patch 0009.  Thanks Elena.
>
> The patch does not apply on top of HEAD as in [1], please post a rebased patch:

Thanks for the heads up.  Here's a rebased version.

-- 
Thanks, Amit Langote
EDB: http://www.enterprisedb.com

Commits

  1. Add SQL/JSON query functions

  2. Add soft error handling to some expression nodes

  3. Adjust populate_record_field() to handle errors softly

  4. Refactor code used by jsonpath executor to fetch variables

  5. Code review for recent SQL/JSON commits

  6. Fix inconsistencies and style issues in new SQL/JSON code

  7. Don't install postmaster symlink anymore

  8. Revert SQL/JSON features

  9. Doc: standardize markup a bit more.