pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alexander Lakhin <exclusion@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Erik Rijkers <er@xs4all.nl>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Amit Langote <amitlangote09@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: vignesh C <vignesh21@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: e.indrupskaya@postgrespro.ru
Subject: Re: SQL/JSON revisited
Date: Wed, 29 Mar 2023 21:00:00 +0300
Message-ID: <60483139-5c34-851d-baee-6c0d014e1710@gmail.com> (raw)
In-Reply-To: <20230329102758.trybzdwbwajrf4mv@alvherre.pgsql>
References: <20230329102758.trybzdwbwajrf4mv@alvherre.pgsql>

Hi,

29.03.2023 13:27, Alvaro Herrera wrote:
> ... and pushed it now, after some more meddling.
>
> I'll rebase the rest of the series now.

Please look at the several minor issues/inconsistencies,
I've spotted in the commit:

1) s/JSON_ARRRAYAGG/JSON_ARRAYAGG/

2)
check_key_uniqueness vs check_unique
IIUC, these are different names of the same entity.

3)
elog(ERROR, "invalid JsonConstructorExprType %d", ctor->type);
vs
elog(ERROR, "invalid JsonConstructorExpr type %d", ctor->type);
I'd choose the latter spelling as the JsonConstructorExprType entity does not exist.

4)
In the block:
     else
     {
         res = (Datum) 0;
         elog(ERROR, "invalid JsonConstructorExpr type %d", ctor->type);
     }
res is assigned but never used.

5)
(expr [FORMAT json_format]) ->? (expr [FORMAT JsonFormat])
(json_format not found anywhere else)

Best regards,
Alexander





view thread (46+ messages)  latest in thread

Message-ID: <60483139-5c34-851d-baee-6c0d014e1710@gmail.com>
Permalink:  ../60483139-5c34-851d-baee-6c0d014e1710@gmail.com/
Also on:    postgresql.org/message-id/60483139-5c34-851d-baee-6c0d014e1710@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: exclusion@gmail.com, alvherre@alvh.no-ip.org, er@xs4all.nl, andrew@dunslane.net, amitlangote09@gmail.com, peter.eisentraut@enterprisedb.com, andres@anarazel.de, vignesh21@gmail.com, e.indrupskaya@postgrespro.ru
  Subject: Re: SQL/JSON revisited
  In-Reply-To: <60483139-5c34-851d-baee-6c0d014e1710@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox