From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Scalia <jayknowsunix@gmail.com>
cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Two PostgreSQL instances returning different output for same
 query
In-reply-to: <C1D9F597-B620-43B4-8561-49A8725BCBA1@gmail.com>
References: <C1D9F597-B620-43B4-8561-49A8725BCBA1@gmail.com>
Comments: In-reply-to John Scalia <jayknowsunix@gmail.com>
	message dated "Tue, 30 Aug 2022 11:21:26 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <3678518.1661875571.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 30 Aug 2022 12:06:11 -0400
Message-ID: <3678519.1661875571@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3678519.1661875571%40sss.pgh.pa.us>
Precedence: bulk

John Scalia <jayknowsunix@gmail.com> writes:
> I=E2=80=99m a bit stumped on this one. For one of my application teams b=
oth their DEV instance and UAT instance are running pg version 12.3 in AWS=
 RDS, and I=E2=80=99ve used the same psql version 13.4.
> The query is a simple:  SELECT to_jsonb(geom) FROM addresses LIMIT 1;

> On both databases the geom field is of data type geometry from postgis, =
but the two dbs are running different versions of Postgis. DEV is 3.0.2 wh=
ile UAT is 2.5.2, but I don=E2=80=99t think this is causing the issue.

I think you're being far too hasty to reject a highly probable
explanation.  Consult the Postgis release notes to see if they
changed anything about casting-to-JSON between those two releases.

A quick look at to_jsonb's innards shows that for a non-core input type,
it will use the type's cast to JSON if there is one, while if there is
not, it will just run the type's output function and call the result a
JSON string.  This seems to fit quite well with the results you show.

			regards, tom lane