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.96) (envelope-from ) id 1vvcE0-00ANKX-0F for pgsql-bugs@arkaria.postgresql.org; Thu, 26 Feb 2026 14:20:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vvcDz-00DI1m-0A for pgsql-bugs@arkaria.postgresql.org; Thu, 26 Feb 2026 14:20:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vvcDy-00DI1b-2H for pgsql-bugs@lists.postgresql.org; Thu, 26 Feb 2026 14:20:18 +0000 Received: from relay2-d.mail.gandi.net ([2001:4b98:dc4:8::222]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vvcDv-00000001JJx-1bS8 for pgsql-bugs@lists.postgresql.org; Thu, 26 Feb 2026 14:20:17 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id BAA1241AA7; Thu, 26 Feb 2026 14:20:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=postgresfriends.org; s=gm1; t=1772115609; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hodgseMohhNjCRTPIo8LSue0Suw8Zcn1+1azqmkujOo=; b=PY30OIuc8LFddacVNTrvAKKvdu2BGis/YPNRPg7Gaubr+NTN4lJ1Lkx9SWkJzTYfguYjft Qgyr1RcU83xmSCNGcimXQqV4kqIz/fG1u/QrTqfSQfJ3PB0hymWvI5aT6o3BEVv5ENyMwR yTWerg7A5b3dpKI4nQL5vdUxf0Tkj9bc2Jfp3MX4yw4G6Z8hwpFvNCvu5+ckloczGGqHfI Qe/OlcR22drtT+NpZkpGCX27V71An3NihnWSgSia/ImG9KK3yGsvebX562eZCN2vaNYClt MJ0KbfLC1AKFEdCnet+gnV6MAc0r91Kv60PQ6gJG9bGprV03S48B7ipC9qZ2oA== Message-ID: <2abdb464-27f5-4759-bb0b-f09ab5b5ceab@postgresfriends.org> Date: Thu, 26 Feb 2026 15:20:08 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 To: lukas.eder@gmail.com, pgsql-bugs@lists.postgresql.org, PG Bug reporting form References: <19418-591ba1f29862ef5b@postgresql.org> Content-Language: en-US From: Vik Fearing In-Reply-To: <19418-591ba1f29862ef5b@postgresql.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-GND-Sasl: vik@postgresfriends.org X-GND-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgddvgeeivdeiucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuifetpfffkfdpucggtfgfnhhsuhgsshgtrhhisggvnecuuegrihhlohhuthemuceftddunecunecujfgurhepkfffgggfuffvfhfhjggtgfesthejredttddvjeenucfhrhhomhepgghikhcuhfgvrghrihhnghcuoehvihhksehpohhsthhgrhgvshhfrhhivghnughsrdhorhhgqeenucggtffrrghtthgvrhhnpeeuffeiudeguddvhefhfedvtdeltddtledttdeuieeiteeggefhjeehhffgieeigfenucfkphepudelhedrieekrdeivddrudefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepudelhedrieekrdeivddrudefpdhhvghloheplgdutddrjedrudehjedrudehvdgnpdhmrghilhhfrhhomhepvhhikhesphhoshhtghhrvghsfhhrihgvnhgushdrohhrghdpqhhiugepueetteduvdegudetteejpdhmohguvgepshhmthhpohhuthdpnhgspghrtghpthhtohepfedprhgtphhtthhopehluhhkrghsvgguvghrsehgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqsghughhssehlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrghdprhgtphhtthhopehnohhrvghplhihsehpohhsthhgrhgvshhqlhdrohhrgh X-GND-State: clean X-GND-Score: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 26/02/2026 10:57, PG Bug reporting form wrote: > The following bug has been logged on the website: > > Bug reference: 19418 > Logged by: Lukas Eder > Email address: lukas.eder@gmail.com > PostgreSQL version: 18.2 > Operating system: Linux > Description: > > When using the ISO/IEC 9075-2:2023(E) 6.34 > syntax, 6.34 GR 4) b) i) says that empty tables should produce a JSON array > with no elements (intuitively), not NULL. > > Try this: > > select json_array(select 1 where false); > > It produces NULL, not [] I can confirm that postgres violates the standard here. -- Vik Fearing