-
Notifications
You must be signed in to change notification settings - Fork 574
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
Adding extension mysql_fdw to postgres-gis #3888
Comments
hi @jahnavisana2812! This issue/error appears to be related the referenced extension, rather than anything with Crunchy Postgres for Kubernetes itself. E.g., nothing here indicates an issue with the Postgres container (e.g. the I therefore suggest trying your question with the maintainers of the extension, e.g. to get better insight into why these Make targets are failing, and what dependencies, setup, etc. is needed to make this work. And in the meantime, I'll leave this issue open in case anyone else out there has any insight and/or ideas to help with your issue. Additionally, I'll note that you can try reaching out via the PGO project community discord as well. |
Update:I have talked to their team and they have insisted to install mysql client library to compile mysql_fdw using sources.I was trying to install mysql client but keeps throwing error Unable to find package.Please suggest the right way to install.I was doing it the following way.
Error: Unable to find a match: mysql-server |
I'm attempting to construct a Dockerfile using the postgres-gis-ubi8 base image. The extension I aim to install is mysql_fdw, a foreign data wrapper allowing PostgreSQL to interact with MySQL. To ensure successful installation, it's necessary to run the makefile. However, I consistently encounter an error with the makefile. I've included the Dockerfile below along with the link to the extension I intend to install. Any assistance would be greatly appreciated. Thanks in advance!
Link of the extension:https://github.com/EnterpriseDB/mysql_fdw
Error I keep getting:
The text was updated successfully, but these errors were encountered: