From: | duc hiep ha <haduchiep(at)googlemail(dot)com> |
---|---|
To: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: ora2pg -c ora2pg.conf -t COPY -a tablename not working properly |
Date: | 2023-08-28 10:11:15 |
Message-ID: | CAM2ukh+=SUxK8QRJs4uGuxiD8OgNQH1=Kv+RMetJj3czD1h-PA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes, you are right.
Thank you
Brs
Hans
Vào Th 2, 28 thg 8, 2023 lúc 14:43 Luca Ferrari <fluca1978(at)gmail(dot)com> đã
viết:
> On Fri, Aug 25, 2023 at 5:49 PM duc hiep ha <haduchiep(at)googlemail(dot)com>
> wrote:
> >
> > Hi,
> >
> > I've just found the root cause! In this command:
> > ora2pg -c ora2pg.conf -t COPY -a tablename
> > I have created and changed the name of table in postgres. It will not
> work like that if i don't put replace_table option in config file.
>
> Out of curiosity: you renamed a table in PostgreSQL after the schema
> was migrated, therefore you need something like
> REPLACE_TABLES old_name:new_name
> in ora2pg, right?
> That explains also why offline mode seemed to work: ora2pg was dumping
> with the original name without asking itself if the table was there in
> PostgreSQL.
>
> Luca
>
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2023-08-28 11:57:37 | Re: Support for Deferred Constraints in PG15 Logical Replication |
Previous Message | Durumdara | 2023-08-28 08:22:46 | Re: Role for just read the data + avoid CREATE / ALTER / DROP |