From: Tom Lane <tgl@sss.pgh.pa.us>
To: tal.tabakman@foretellix.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19110: the order of elements in a json object in database is
 different then the order of elements
In-reply-to: <19110-dffefa888c44b48f@postgresql.org>
References: <19110-dffefa888c44b48f@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 11 Nov 2025 14:26:34 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2183807.1762874163.1@sss.pgh.pa.us>
Date: Tue, 11 Nov 2025 10:16:03 -0500
Message-ID: <2183808.1762874163@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2183808.1762874163%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> This hash map is stored as a json object under a column defined as a json
> column (and not jsonb)
> what we are noticing is that when we send the relevant object from our
> application to postgres and fetch it back (using update and select queries
> respectivally) , the order of elemenet in the hash map is changing which
> causes a problem in our end.

The only way this could possibly be happening on the Postgres server
side is if the value is being cast to jsonb on its way to the table.
I'd check issues like how the prepared statement's parameter is
declared.

If you are going through JDBC or another client-side stack, it's
possible that that is substituting jsonb for json in the command
issued to the server.  You might need to pretend that the parameter
is plain text to avoid that.

			regards, tom lane