From: | WR <wolle321(at)freenet(dot)de> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Access a newer Version of PGDB (v13) with an older libpq (v10 x86) |
Date: | 2021-05-03 09:15:11 |
Message-ID: | 0a6cd677-b7f1-ed10-97d5-d62ada5d3d19@freenet.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Am 03.05.2021 um 10:41 schrieb Laurenz Albe:
> On Sat, 2021-05-01 at 12:59 +0200, Wolfgang Rißler wrote:
>> Am 30.04.2021 um 16:16 schrieb Tom Lane:
>>> I would recommend trying to use a reasonably late-vintage libpq; we do
>>> fix bugs in it on a regular basis.
>>> The common stumbling block for cross-version situations is that the
>>> client makes assumptions about system catalog contents that are not
>>> valid in some other server release. libpq proper doesn't really touch
>>> the catalogs, so it's mostly impervious to that problem; but you'll need
>>> to test your applications.
>>
>> Of course we'll do. One thing is, that we load and write bytea's. And as
>> I read, there have been some changes. All other Operations are less
>> problematic.
>
> Version 9.0 changed the default "bytea" output format to hexadecimal.
> If you want the old text output format, set "bytea_output" to "escape".
>
> If you output "bytea"s in binary form, nothing has changed.
>
This is a useful hint. I did this already in my PG10 <-> libpq10(x86)
testinstallation.
Thank you.
--
May the source be with you
From | Date | Subject | |
---|---|---|---|
Next Message | Hans Buschmann | 2021-05-03 10:26:25 | Huge performance penalty with parallel queries in Windows x64 v. Linux x64 |
Previous Message | Adrien Nayrat | 2021-05-03 08:58:44 | Re: "invalid contrecord" error on replica |