Another possibility is to use an untrusted interpreted PL such as
plperlu. That avoids the need for C. Or maybe you could prototype using
plperlu and then translate to C when it's all working. It all depends on
your needs.
cheers
andrew
Lane Van Ingen wrote:
>That sounds good, and about what I expected. I am not a C programmer, but
>have
>access to others who are. Where would I need to put the C function in order
>to
>have PostgreSQL find it? Any special considerations other than putting it in
>'the right library' ??
>
>-----Original Message-----
>From: Jonah H. Harris [mailto:jonah.harris@gmail.com]
>Sent: Monday, October 10, 2005 3:49 PM
>To: Lane Van Ingen
>Cc: pgsql-hackers@postgresql.org
>Subject: Re: [HACKERS] Need A Suggestion
>
>
>In the past, I've just written a C-based function that calls out to system.
>
>
>2005/10/10, Lane Van Ingen <lvaningen@esncc.com>:
>
>
>>I am working on the development of a military application which uses
>>PostgreSQL trigger functions. I cannot (unfortunately) tell you specify
>>
>>
>use,
>
>
>>being as it is classified.
>>
>>What I need the ability to occasionally call (execute) a .exe program
>>
>>
>object
>
>
>>outside of the database from within the function (either during or at the
>>end of the function would be acceptable), giving an explicit path and
>>command line parameters. It is understood that in doing such the call will
>>need to be brief in order to avoid slowing up PostgreSQL in any way. Can
>>anybody make a suggestion as to how to do that, or inform me if there is a
>>way to do thisa lready?
>>
>>I have already consulted to other mailing lists for help, with no results.
>>
>>
>I
>
>
>>am a Windows 2003 user, version 8.0.1
>>
>>
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 2: Don't 'kill -9' the postmaster
>>
>>
>>
>
>
>--
>Respectfully,
>
>Jonah H. Harris, Database Internals Architect
>EnterpriseDB Corporation
>http://www.enterprisedb.com/
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
>
>