-
Notifications
You must be signed in to change notification settings - Fork 569
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
Relation 'pg_indexes' unknown #11697
Labels
Comments
mfussenegger
added
complexity: no estimate
feature: integration
Better integration with other systems
feature: pgsql
and removed
triage
An issue that needs to be triaged by a maintainer
labels
Sep 6, 2021
mfussenegger
added a commit
that referenced
this issue
Sep 7, 2021
Closes #11697 Given that there are no `CREATE INDEX` statements in CrateDB the table is empty.
5 tasks
mfussenegger
added a commit
that referenced
this issue
Sep 7, 2021
Closes #11697 Given that there are no `CREATE INDEX` statements in CrateDB the table is empty.
Dear @mfussenegger, thank you for providing an improvement through #11706 so quickly. I will let you know about the outcome with respect to crate/cratedb-examples#4. With kind regards, |
mfussenegger
added a commit
that referenced
this issue
Sep 8, 2021
Closes #11697 Given that there are no `CREATE INDEX` statements in CrateDB the table is empty.
mergify bot
pushed a commit
that referenced
this issue
Sep 8, 2021
Closes #11697 Given that there are no `CREATE INDEX` statements in CrateDB the table is empty.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Hi there,
this is merely a notice where the compatibility with PostgreSQL can be improved.
On behalf of crate/cratedb-examples#4, I conducted some experiments about how to export data from InfluxDB and import into CrateDB the other day.
The outcome was that the influxdb-write-to-postgresql program croaked with
ERROR: Relation 'pg_indexes' unknown
, when trying to import data into CrateDB.With kind regards,
Andreas.
The text was updated successfully, but these errors were encountered: