-
-
Notifications
You must be signed in to change notification settings - Fork 528
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
PGLOADER.CATALOG:INDEX error #1289
Comments
MikeN123
pushed a commit
to semestry/pgloader
that referenced
this issue
Aug 20, 2021
This makes sure we do not select dependencies form the pg_operator class or other similar things. Fixes dimitri#1289
marcokrikke
pushed a commit
to semestry/pgloader
that referenced
this issue
Nov 30, 2023
This makes sure we do not select dependencies form the pg_operator class or other similar things. Fixes dimitri#1289
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pgloader --version
did you test a fresh compile from the source tree?
Compiling pgloader from sources is documented in the
README, it's
easy to do, and if patches are to be made to fix your bug, you're going
to have to build from sources to get the fix anyway…
did you search for other similar issues?
how can I reproduce the bug?
Include a self-contained pgloader command file.
If you're loading from a database, consider attaching a database dump to
your issue. For MySQL, use
mysqldump
. For SQLite, just send over yoursource file, that's easy. Maybe be the one with your production data, of
course, the one with just the sample of data that allows me to reproduce
your bug.
When using a proprietary database system as a source, consider creating
a sample database on some Cloud service or somewhere you can then give
me access to, and see my email address on my GitHub profile to send me
the credentials. Still open a public issue for tracking and as
documentation for other users.
I can provide additional details if needed, but this is the end of the log. I have an identical server with a (theoretically) identical schema where I don't get this error. Haven't run a compare of the schemas but they were the same a couple of months ago and should be in sync. If I run the last query in the log manually, I get 2 rows back.
The text was updated successfully, but these errors were encountered: