> Hmm. If that's true, then the failure to get a sema would occur very
> early in the new backend's lifetime, before it's had a chance to
> create any trouble. Maybe the very easiest solution to the sema issue
> is to make the new backend send a failure report to its client and
> then exit(0) instead of exit(1), so that the postmaster considers it a
> clean exit rather than a crash...
Sounds like the cleanest solution too. If it pans out, I like it...
- Tom