From: Bruce Momjian <bruce@momjian.us>
To: Sbob <sbob@quadratum-braccas.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: DB Encoding question
Date: Mon, 22 Aug 2022 12:40:50 -0400
Message-ID: <YwOxkk0X0Ikp0baG@momjian.us> (raw)
In-Reply-To: <3529b018-3fd6-0d60-02b1-06ee5db9ba82@quadratum-braccas.com>
References: <3529b018-3fd6-0d60-02b1-06ee5db9ba82@quadratum-braccas.com>
On Mon, Aug 22, 2022 at 10:20:41AM -0600, Sbob wrote:
> All;
>
>
> We are converting from DB2 on the mainframe to PostgreSQL 14 in the cloud.
> We have been using IIDR to dump DB2 tables to CSV files and then using
> pg_loader / COPY to import the files. However the DB2 Encoding is EBCDIC and
> the PostgreSQL db encoding is UTF8, this is causing some rows / columns to
> fail when we try to load the data into PostgreSQL
>
> Will we be better off changing the PostgreSQL encoding to match the DB2
> database? Will this cause other issues down the road? Is there a 'best
> practice' for this use case?
I would convert the dump file to be UTF8 using iconv and then load it.
I would also suggest setting the _client_ encoding to EBCDIC and have
the server encoding be UTF8, but we don't support EBCDIC as far as I can
tell.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
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-admin@postgresql.org
Cc: bruce@momjian.us, sbob@quadratum-braccas.com, pgsql-admin@lists.postgresql.org
Subject: Re: DB Encoding question
In-Reply-To: <YwOxkk0X0Ikp0baG@momjian.us>
* 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