From: | "Sonnenberg-Carstens, Stefan" <ssonnenberg(at)ophardt(dot)com> |
---|---|
To: | Mark Teper <mark(dot)teper(at)gmail(dot)com>, "pgsql-sql(at)lists(dot)postgresql(dot)org" <pgsql-sql(at)lists(dot)postgresql(dot)org> |
Subject: | AW: |
Date: | 2019-05-06 08:17:46 |
Message-ID: | 4251b7dca6bf4536b4d5a11931a83191@OPHT402P.ophardt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi,
is the Python code running inside the PostgreSQL instance?
If not, the performance penalty might only get marginally better because it always involves to copy the data to the client and back again.
Mit freundlichen Grüßen
Stefan Sonnenberg-Carstens
Teamleiter Softwareentwicklung WECO / DevOps Engineer
B.Sc. Wirtschaftsinformatik
[Signatur_50-Jahre-ingo-man]
OPHARDT HYGIENE-TECHNIK GmbH + Co. KG
Lindenau 27
D - 47661 Issum
Tel: +49 2835 18-492
Fax: +49 2835 18-28492
Mail: ssonnenberg(at)ophardt(dot)com<mailto:ssonnenberg(at)ophardt(dot)com>
www.OPHARDT.com<http://www.ophardt.com/>
Handelsregistereintrag beim Amtsgericht Kleve:
Kommanditgesellschaft HRA 1681, Komplementärin:
OPHARDT HYGIENE-TECHNIK VerwaltungsGmbH HRB 3910
Geschäftsführer: Thomas Houcken
USt.-Identifikations-Nr.: DE813067257
CONFIDENTIALITY NOTICE:
This e-mail communication and any attachments may contain confidential and privileged information for the use
of the designated recipients named above. Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies
of the original message.
Von: Mark Teper [mailto:mark(dot)teper(at)gmail(dot)com]
Gesendet: Donnerstag, 2. Mai 2019 19:51
An: pgsql-sql(at)lists(dot)postgresql(dot)org
Betreff:
Hi,
I'm trying to build some numerical processing algorithms on Postgres Array data types. Using PL/Python I can get access to the numpy libraries but the performance is not great. A guess is that there is a lot of overhead going from Postgres -> Python List -> Numpy and back again.
I'd like to test if that's the issue, and potentially fix by creating a C extension to convert directly from Postgres Array types to Numpy Array types. I _think_ I have the C side somewhat working, but I can't get Postgres to use the transform.
What I have:
---
CREATE FUNCTION arr_to_np(val internal) RETURNS internal LANGUAGE C AS 'MODULE_PATHNAME', 'arr_to_np';
CREATE FUNCTION np_to_arr(val internal) RETURNS real[] LANGUAGE C AS 'MODULE_PATHNAME', 'np_to_arr';
CREATE TRANSFORM FOR real[] LANGUAGE plpythonu (
FROM SQL WITH FUNCTION arr_to_np(internal),
TO SQL WITH FUNCTION np_to_arr(internal)
);
CREATE FUNCTION fn (a integer[]) RETURNS integer
TRANSFORM FOR TYPE real[]
AS $$ return a $$ LANGUAGE plpythonu;
----
The problem is this produces an error that transforms for type "real" doesn't work. It doesn't seem to allow for transforms on array's as opposed to underlying types. Is it possible to tell it to apply the transform to the array?
Thanks,
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Teper | 2019-05-06 09:32:40 | Re: plpython transforms vs. arrays |
Previous Message | Kirti Adesara | 2019-05-04 16:38:07 | create role/user management |