BUG #17572: Different behaviour in different versions of postgresql details as in email

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: rujuljain123(at)gmail(dot)com
Subject: BUG #17572: Different behaviour in different versions of postgresql details as in email
Date: 2022-08-04 17:32:28
Message-ID: 17572-9787e20f560d6eb8@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17572
Logged by: Rujul Jain
Email address: rujuljain123(at)gmail(dot)com
PostgreSQL version: 14.4
Operating system: Linux
Description:

On our development server , we have used (on windows)
PostgreSQL 14.2, compiled by Visual C++ build 1914, 64-bit

On our production server, we have used (on linux Centos 7)
PostgreSQL 14.4 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623
(Red Hat 4.8.5-44), 64-bit

We have noticed the difference in behavior while reading column of type
BYTEA from our tables

In development server, when this value is converted to TEXT, it doesnt start
and end with double quotes.

But In production server, when this value is converted to TEXT, it starts
and ends with double quotes.

We have checked the following commands, they return same value in Postgresql
server of development and production.

SHOW SERVER_ENCODING;
SHOW CLIENT_ENCODING;
SELECT * FROM information_schema.character_sets where
default_collate_catalog = '[dbname]';

Pls suggest what we are missing.Do you think downgrading Postgresql on Linux
to 14.2 version will fix the issue?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2022-08-04 18:14:53 Re: BUG #17572: Different behaviour in different versions of postgresql details as in email
Previous Message Julien Rouhaud 2022-08-04 17:26:09 Re: BUG #17571: PostgreSQL 15b2 ICU collation defined at db level sorts differently in collate clause vs implicit