Hi Uwe,
I think Martin was right with this one. You are probably going to
have to edit the export file from mysqldump to remove the inserts for
tables that the Postgres schema maker creates automatically. To make
this easier, so you don't have to recreate the schema each time, you can
use transactions. So run "BEGIN WORK;", import the dump file, if
something throws an error enter "ROLLBACK WORK;" and edit out those
lines, then try again from "BEGIN WORK;" Once it runs without errors do
"COMMIT WORK;" to save the import state.
On 2022-08-30 13:41, Martin Simmons wrote:
On Tue, 30 Aug 2022 16:04:08 +0200, Uwe Schuerkamp said:
Hello Charles,
thanks for "INSERT only" idea... it's worked partially. After removing
some double quotes and other characters using sed psql didn't like,
the import runs for a while and then stops with the following error:
INSERT 0 6
ERROR: duplicate key value violates unique constraint "status_pkey"
DETAIL: Key (jobstatus)=(A) already exists.
Any idea what could be causing this?
That looks like the JobStatus table. Don't migrate that one because the
make_postgresql_tables script inserts all of the rows that are needed.
__Martin
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
