Bill Studenmund <[EMAIL PROTECTED]> writes: > All ECHILD is doing is saying there was no child. Since we aren't really > waiting for the child, I don't see how that's a problem. You're missing the point: on some platforms the system() call is returning a failure indication because of ECHILD. It's system() that's broken, not us, and the issue is how to work around its brokenness without sacrificing more error detection than we have to. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
- Re: [HACKERS] SIGCHLD handler in Postgres C function. Tom Lane
- Re: [HACKERS] SIGCHLD handler in Postgres C function. Tatsuo Ishii
- Re: [HACKERS] SIGCHLD handler in Postgres C function. Bill Studenmund
- Re: [HACKERS] SIGCHLD handler in Postgres C function. Tom Lane
- Re: [HACKERS] SIGCHLD handler in Postgres C function. Bill Studenmund
- Re: [HACKERS] SIGCHLD handler in Postgres C function. Tom Lane
- Re: [HACKERS] SIGCHLD handler in Postgres C function. Bill Studenmund
- Re: [HACKERS] SIGCHLD handler in Postgres C function. Bruce Momjian
- Re: [HACKERS] SIGCHLD handler in Postgres C function. Tom Lane
- Re: [HACKERS] SIGCHLD handler in Postgres C function. Bruce Momjian