-
Notifications
You must be signed in to change notification settings - Fork 32
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
Support request for pgsql-13.x #24
Comments
Yeah the thing I've been waiting for is a docker image that has multicorn support. The code should work if you're happy to set that up yourself. You can see the |
The current postgres:13 docker image is debian 10.9 (buster) while postgresql-13-python3-multicorn is in 11 (sid) |
The fdw should work with postgres 13. I'm just not advertising that due to being unable to test it. |
Yes, I tried with bitnami/postgresql 13 chart, but no luck, maybe I was missing something there... But Anyhow. Thanks, Matthew for your quick response. |
Since you have been so nice about this I've had another look. I was able to install the required package from sid onto buster (which is a bad idea in general - I would not recommend this for production use). The fdw does work. For your specific use case I recommend installing multicorn on the virtual machine. You may have to do it from source. See the documentation for details. If this resolves your issue then please close this ticket. I may be able to help you if you have trouble setting up the fdw. |
Hello Matthew, I have used Kubernetes to set up postgresql-ha 13.2 version. And as you suggested, I tried installing Multicorn from the source, but It was failing to install and showing up errors.
Couldn't figure out what's wrong in the make file. Appreciate your help !! |
You could try installing it with pgxn: https://pgxn.github.io/pgxnclient/install.html
|
Sorry Matthew, even "pgxn install multicorn" didn't work:
|
:( https://github.com/Segfault-Inc/Multicorn/issues ... I see you've already done that heh. Good luck! |
Yes Matthew, I was about to post that here for ur reference. There seems to be an issue with the Multicorn setup itself. But anyhow will wait for their response. Thanks for ur time, Matthew. |
FWIW. I'm a big fan of this extension and I've also been waiting for.
pg13. I've running into the same Multicorn roadblock. Does anyone know
the core developers of Multicorn?
I'm copying my friend Jan Wieck on this thread. I know he's a multicorn
fan and I know he's techie enough to fix whatever Python3/Pg13 multcorn
issue is the blocker if we need to fork multicorn so that esfdw may live.
…--Denis
PS For those who haven't heard of Jan. He's a bit of a Postgres legend (at
least in his own mind) :-). Seriously, Jan is an Emeritus Core team
member and is the original author of several cornerstone features of
Postgres such as PLpgSQL, Toast, Referential Integrity, ... Jan, as you
can see, I'm trying to win you over to help us with public flattery.
Please do not let it go to your head. ;-)
On Fri, Apr 9, 2021 at 2:04 PM Saketha016 ***@***.***> wrote:
Yes Matthew, I was about to post that here for ur reference.
Segfault-Inc/Multicorn#261
<Segfault-Inc/Multicorn#261>
There seems to be an issue with the Multicorn setup itself. But anyhow
will wait for their response. Thanks for ur time, Matthew.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMWOHR6IZE23VIKROQC52TTH46RVANCNFSM42TMTV5A>
.
|
I found the exact same PG-13 incompatibilities that are in the pull
request Segfault-Inc/Multicorn#260
With those I can build and install on CentOS 8 and then successfully
CREATE EXTENSION multicorn;
Any idea what is holding that up? There is some mention about random
errors, but I couldn't find anything specific about what those errors are.
Regards, Jan
…On 4/10/21 12:23 AM, Denis Lussier wrote:
FWIW. I'm a big fan of this extension and I've also been waiting for.
pg13. I've running into the same Multicorn roadblock. Does anyone
know the core developers of Multicorn?
I'm copying my friend Jan Wieck on this thread. I know he's a multicorn
fan and I know he's techie enough to fix whatever Python3/Pg13 multcorn
issue is the blocker if we need to fork multicorn so that esfdw may live.
--Denis
PS For those who haven't heard of Jan. He's a bit of a Postgres legend
(at least in his own mind) :-). Seriously, Jan is an Emeritus Core
team member and is the original author of several cornerstone features
of Postgres such as PLpgSQL, Toast, Referential Integrity, ... Jan,
as you can see, I'm trying to win you over to help us with public
flattery. Please do not let it go to your head. ;-)
On Fri, Apr 9, 2021 at 2:04 PM Saketha016 ***@***.***
***@***.***>> wrote:
Yes Matthew, I was about to post that here for ur reference.
Segfault-Inc/Multicorn#261
<Segfault-Inc/Multicorn#261>
There seems to be an issue with the Multicorn setup itself. But
anyhow will wait for their response. Thanks for ur time, Matthew.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMWOHR6IZE23VIKROQC52TTH46RVANCNFSM42TMTV5A>.
--
Jan Wieck
Postgres User since 1994
|
Thanks to the work of @luss, this ticket can be resolved. The recommended way to install this FDW on PostgreSQL 13+ is to use Multicorn 2. Please review the installation instructions for that repo. |
Hi!
As PostgreSQL 13 offers significant improvements in performance and usability, want to know whether any plan to support pgsql-13 version in the future.
The text was updated successfully, but these errors were encountered: