pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17572: Different behaviour in different versions of postgresql details as in email
2+ messages / 2 participants
[nested] [flat]
* BUG #17572: Different behaviour in different versions of postgresql details as in email
@ 2022-08-04 17:32 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2022-08-04 17:32 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: rujuljain123@gmail.com
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?
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #17572: Different behaviour in different versions of postgresql details as in email
@ 2022-08-04 18:14 David G. Johnston <david.g.johnston@gmail.com>
parent: PG Bug reporting form <noreply@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: David G. Johnston @ 2022-08-04 18:14 UTC (permalink / raw)
To: rujuljain123@gmail.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
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.
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2022-08-04 18:14 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-08-04 17:32 BUG #17572: Different behaviour in different versions of postgresql details as in email PG Bug reporting form <noreply@postgresql.org>
2022-08-04 18:14 ` David G. Johnston <david.g.johnston@gmail.com>
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