Search Postgresql Archives

Sharing database handles across forked child processes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



How does Postgres handle sharing database handles across child processes?
That is, if I have a process that opens a connection to the database and
then forks a few child processes, what happens?


Can the child processes safely use the handle?


If one child closes the handle, what happens to the handle in all the
other children? The parent?

This isn't a great thing to do, I realize, but I'm wedging database access
into an existing heavily fork-bound perl program, so my hands are somewhat
tied architecturally. (If it means I have to constantly test to see if the
handle's valid, and may have to deal with a handle randomly going away on
me, I can handle that -- I'm more worried about data corruption and
deadlock problems here, stuff I can't reasonably catch at the application
level)

-Dan



---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
       message can get through to the mailing list cleanly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux