Re: Function written in C, hangs on one machine and not another... - Mailing list pgsql-general

From Dennis Jenkins
Subject Re: Function written in C, hangs on one machine and not another...
Date
Msg-id 20051028151823.19464.qmail@web81305.mail.yahoo.com
Whole thread Raw
In response to Re: Function written in C, hangs on one machine and not another...  (Douglas McNaught <doug@mcnaught.org>)
Responses Re: Function written in C, hangs on one machine and not another...  (Douglas McNaught <doug@mcnaught.org>)
List pgsql-general

--- Douglas McNaught <doug@mcnaught.org> wrote:

> CG <cgg007@yahoo.com> writes:
>
> > Does this give you any more insight into an
> alternate method of getting this
> > thing done?
>
> I would fork(), set up file descriptors
> appropriately, then have the
> child call the Adobe library and the parent feed the
> data to it.
> Once the document is loaded in the child, do
> whatever processing you
> need to, then pass the results back to the parent
> via stdout or a
> temporary file.
>
> Ugly, but probably the most robust way to do it.
> Make sure you don't
> call any PG-internal functions in the child process,
> as that will
> confuse things badly.
>

Is it safe for the postgres engine to fork()?  Would
the child need to close down anything immediately in
its main() to avoid corrupting the parent?


Dennis Jenkins

pgsql-general by date:

Previous
From: Dennis Jenkins
Date:
Subject: Re: Function written in C, hangs on one machine and not another...
Next
From: Douglas McNaught
Date:
Subject: Re: Function written in C, hangs on one machine and not another...