-
-
Notifications
You must be signed in to change notification settings - Fork 541
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
postgres -> postgres include/exclude logic not working correctly #1556
Comments
Facing a similar issue. My set up is slightly different, but the symptom seems to be the same. I'm running in a docker container, so I didn't do a fresh build locally. My Dockerfile is very basic: I have a subset of tables I want to migrate from sqlserver (2016) -> postgres. The source and target DBs are hosted in docker containers as well. This example only has a single table, as it reproduces the error consistently (my ms.load file can be seen in the log below). I'm setting a fetch limit to avoid hitting out of heap errors. I run pgloader with -d and -v to see what information i could get:
I'm not an expert on sqlserver, but I believe there is an issue in the last query using kcu1 rather than KCU1 as the table alias. Running a simple query (just via SQL Server Management Studio):
Removing the |
pgloader --version
did you test a fresh compile from the source tree?
yes
yes - issue #1153 similar, but was not resolved/progressed
I am expecting it to NOT load the table schema1.films_staging
I am also expecting to see schema1.films_me, schema2.films, schema2.filmes_staging being copied
Instead, it is copying only schema1.films_staging - it is as though the exclude is inverted.
Ultimately, I am trying to achieve something like this config:
successfully copy all tables from schema1 and schema2, excluding any tables in schema1 or schema2 that match the string *_staging
Further explanation:
src database:
destination database before running pgloader:
run pgloader my.loader
destination database after running pgloader
The text was updated successfully, but these errors were encountered: