From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: rujuljain123@gmail.com
Subject: BUG #17572: Different behaviour in different versions of postgresql details as in email
Date: Thu, 04 Aug 2022 17:32:28 +0000
Message-ID: <17572-9787e20f560d6eb8@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17572
Logged by: Rujul Jain
Email address: rujuljain123@gmail.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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, rujuljain123@gmail.com
Subject: Re: BUG #17572: Different behaviour in different versions of postgresql details as in email
In-Reply-To: <17572-9787e20f560d6eb8@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox