From: andrew@corvus.biomed.brown.edu
To: pgsql-interfaces@postgresql.org
Subject: Python as a procedural language
Date: Wed, 4 Apr 2001 21:15:34 -0400
Message-ID: <20010404211534.A13150@corvus.biomed.brown.edu> (raw)
Hi
I've coded up a module that implements python as a procedural language
for postgresql. A tarball can be downloaded at
http://users.ids.net/~bosma
If anyone is interested, take a look at it. Comments and suggestions
would be appreciated. Functions and triggers work. The SPI interface
can run execute queries and saved plans. I'm sure there's a bug or
three still lurking in there. Installation instructions are in the
tarball. The only complication is that for python to load its dynamic
modules without unresolved symbols, the flags passed to dlopen need to
be modified. This means you will have to rebuild postgres. Is there
any reason why the default dlopen is called without the RTLD_GLOBAL
flag? (Actually you can build without modifying postgres, but that
requires explicitly linking python loadable modules to the language
module.)
Thanks
Andrew Bosma
--
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: andrew@corvus.biomed.brown.edu
Subject: Re: Python as a procedural language
In-Reply-To: <20010404211534.A13150@corvus.biomed.brown.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox