| From: | "James A(dot) Robinson" <jim(dot)robinson(at)gmail(dot)com> |
|---|---|
| To: | srkrishna1(at)aol(dot)com |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Copy data from DB2 (Linux) to PG |
| Date: | 2018-11-01 18:05:03 |
| Message-ID: | CAPd04b6DkxWsz0DFJFVsz7UKTtaj658g_MYeRpvMaMfFvZNQ0Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Nov 1, 2018 at 10:50 AM Ravi Krishna <srkrishna1(at)aol(dot)com> wrote:
> [...] What I need is a constant refresh.
> We plan to use it daily to replicate data from db2 to pg.
Perhaps you've already considered and discarded the idea, but your use
case made me think back to when I was looking at AWS SCT as a way to
migrate ourselves off a legacy DB into MySQL. It looks as though it
has support for converting from DB2 to Postgres as well, and if I
recall correctly it had facilities for ongoing replication.
https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.DB2LUW.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2018-11-01 20:06:08 | Truncated queries in the pg_log file |
| Previous Message | Ravi Krishna | 2018-11-01 17:49:57 | Re: Copy data from DB2 (Linux) to PG |