Re: Function written in C, hangs on one machine and not another...
От
Dennis Jenkins
Тема
Re: Function written in C, hangs on one machine and not another...
Дата
Msg-id
20051028151823.19464.qmail@web81305.mail.yahoo.com
Ответ на
Re: Function written in C, hangs on one machine and not another... (Douglas McNaught)
Список
Дерево обсуждения
Function written in C, hangs on one machine and not another... CG <cgg007@yahoo.com>
Re: Function written in C, hangs on one machine and not another... Martijn van Oosterhout <kleptog@svana.org>
Re: Function written in C, hangs on one machine and not another... CG <cgg007@yahoo.com>
Re: Function written in C, hangs on one machine and not another... Martijn van Oosterhout <kleptog@svana.org>
Re: Function written in C, hangs on one machine and not another... CG <cgg007@yahoo.com>
Re: Function written in C, hangs on one machine and not another... Dennis Jenkins <dennis.jenkins@sbcglobal.net>
Re: Function written in C, hangs on one machine and not another... Douglas McNaught <doug@mcnaught.org>
Re: Function written in C, hangs on one machine and not another... Dennis Jenkins <dennis.jenkins@sbcglobal.net>
Re: Function written in C, hangs on one machine and not another... Douglas McNaught <doug@mcnaught.org>
Re: Function written in C, hangs on one machine and not another... Martijn van Oosterhout <kleptog@svana.org>
Re: Function written in C, hangs on one machine and not another... Douglas McNaught <doug@mcnaught.org>
Re: Function written in C, hangs on one machine and not another... CG <cgg007@yahoo.com>
Re: Function written in C, hangs on one machine and not another... Douglas McNaught <doug@mcnaught.org>
--- Douglas McNaught wrote: > CG 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 по дате отправления
От: Dennis Jenkins
Дата:
От: Douglas McNaught
Дата: