Thread: BUG #17572: Different behaviour in different versions of postgresql details as in email
BUG #17572: Different behaviour in different versions of postgresql details as in email
From
PG Bug reporting form
Date:
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?
Re: BUG #17572: Different behaviour in different versions of postgresql details as in email
From
"David G. Johnston"
Date:
On Thu, Aug 4, 2022 at 11:00 AM PG Bug reporting form <noreply@postgresql.org> wrote:
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
If you can provide a self-contained demonstration of the behavior using a self-contained psql script (show your output of running it via shell on both machines) that would help.
David J.