From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | John Scalia <jayknowsunix(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Two PostgreSQL instances returning different output for same query |
Date: | 2022-08-30 16:20:03 |
Message-ID: | 20220830162002.GA20650@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Aug 30, 2022 at 11:21:26AM -0400, John Scalia wrote:
> I’m a bit stumped on this one. For one of my application teams both their DEV instance and UAT instance are running pg version 12.3 in AWS RDS, and I’ve 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 while UAT is 2.5.2, but I don’t think this is causing the issue.
Changelog for postgis 3.0.0 shows:
3687, Casts json(geometry) and jsonb(geometry) for implicit GeoJSON generation (Paul Ramsey)
looks to be very related.
Best regards,
depesz
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2022-08-30 17:29:17 | Re: max_wal_size and wal_keep_size |
Previous Message | Tom Lane | 2022-08-30 16:06:11 | Re: Two PostgreSQL instances returning different output for same query |