You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
did you test a fresh compile from the source tree?
No.
did you search for other similar issues?
Yes.
how can I reproduce the bug?
Load file with:
LOAD DATABASE
FROM mysql://<connection string>
INTO postgresql://<connection string>
WITH data only, truncate, disable triggers, downcase identifiers, reset sequences,
workers = 8, concurrency = 1, prefetch rows = 500, batch rows = 500,
single reader per thread, on error stop
pgloader output you obtain
2024-06-26T12:12:52.888381-04:00 LOG report summary reset
table name errors read imported bytes total time read write
--------------------------------------------------- --------- --------- --------- --------- -------------- --------- ---------
fetch meta data 0 109 109 0.201s
Drop Foreign Keys 0 0 0 0.000s
Truncate 0 53 53 0.255s
--------------------------------------------------- --------- --------- --------- --------- -------------- --------- ---------
I see it indicated 'Truncate' , but I suspect table is not being truncated as subsequently the COPY fails with 'Duplicate Primary key constraint violation'.
After the run I still see the old rows in the table.
data that is being loaded, if relevant
How the data is different from what you expected, if relevant
I am looking to migrate data only, the script failed, on re-running was expecting it to 'detect there is data in the target table on postgres and expecting it to truncate the table prior to running the COPY of the data.
Is there a way to DUMP/Log the SQL pgloader runs for 'truncate'? so I can verify the '53 truncates' it indicates above?
The text was updated successfully, but these errors were encountered:
I did a test with just this one table in MySQL. I am using a MATERIALIZE VIEWS to copy the data and finding it does not 'truncate' the data in target Postgres table when I use MATERIALIZE VIEWS.
My Load file has:
MATERIALIZE VIEWS view_name AS $$ <select from original_table_table> $$
EXCLUDING TABLE NAMES MATCHING 'original_table_name'
INCLUDING ONLY TABLE NAMES MATCHING 'view_name'
ALTER TABLE NAMES MATCHING 'view_name' RENAME TO 'pg_table_name'
So how can I specify the 'target table should be truncated' (e.g. pg_table_name) when using MATERIALIZE VIEW with renaming tables from source to target?
No.
Yes.
Load file with:
I see it indicated 'Truncate' , but I suspect table is not being truncated as subsequently the COPY fails with 'Duplicate Primary key constraint violation'.
After the run I still see the old rows in the table.
I am looking to migrate data only, the script failed, on re-running was expecting it to 'detect there is data in the target table on postgres and expecting it to truncate the table prior to running the COPY of the data.
Is there a way to DUMP/Log the SQL pgloader runs for 'truncate'? so I can verify the '53 truncates' it indicates above?
The text was updated successfully, but these errors were encountered: