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 1wzwCb-004LdG-2x for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Aug 2026 13:01:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wzwCa-007aGe-0B for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Aug 2026 13:01:00 +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.96) (envelope-from ) id 1wzvvK-007XL6-07 for pgsql-bugs@lists.postgresql.org; Fri, 28 Aug 2026 12:43:10 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wzvvH-00000001ige-1JoU for pgsql-bugs@lists.postgresql.org; Fri, 28 Aug 2026 12:43:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=KqYUAsGDc47+ZbeMRK+OboRx7tc2uprc9Ka8l7vhT+c=; b=l8d1j6Zeu+4u+YGqT09LK+h2bA RlnI/mLz6fDpAViYLr0N8zUI2T+j6pK70HKo9s8Qy0/ehqWXLtVUSYjuQEBSKeRREb4qCOfCKuwKY XYHtBD3ssB8iOpcQL3m+vZslLWtpp4nI8weRSOqEExq4Ek6u3BiVH5ivld7QORm2UlqTXLa+Mh4ot e8ukwKf8EhH0ISkPnc0cDIzqR1qvtSg89qyPgKC0WUJi4a2ckgh6msl0k59gdfgW6sL9lQLdv4Dij LNFnxtW7l3yKZAYXvIRnfP+JP3ZTj1xj1MATc3WhGgzu3j4AUuVGjWAVT8mvIww5cgIL/E2fO6IXj Izz+YIoQ==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wzvvF-008cXc-2d for pgsql-bugs@lists.postgresql.org; Fri, 28 Aug 2026 12:43:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1wzvvD-00000005fHp-3zrO for pgsql-bugs@lists.postgresql.org; Fri, 28 Aug 2026 12:43:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19643: Output of jsonb_populate_recordset not consistent with documentation description To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: yishundinesh@gmail.com Reply-To: yishundinesh@gmail.com, pgsql-bugs@lists.postgresql.org Date: Fri, 28 Aug 2026 12:42:44 +0000 Message-ID: <19643-eadf5dc7e134dd3e@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19643 Logged by: Balaji Venkatesan Email address: yishundinesh@gmail.com PostgreSQL version: 18.6 Operating system: Ubuntu Description: =20 As per the documentation jsonb_populate_record "Expands the object in from_json to a row whose columns match the record type defined by base". The example given the documentation is working fine, but if I replace null::myrow with Row(('a'::text,'b'::text), the output discards from_json(second argument completely) First argument's value is being used instead of using it as a key Eg: select * from jsonb_populate_recordset(ROW('a'::text,'b'::text),'[{"a":"test","b":"55"}]') as (a text, b text) Output:: a,b Expected output: test,55