Why does Postgres need the /bin/sh?

Hey guys... second post of the day.  If you read my last post about
Postgres 7.2.1 segfaulting on Slackware 8.0, you noted I am trying to
chroot Postgres.  Unfortunately, my chrooted postgres cannot create
databases due to a 'system' call, which runs '/bin/sh'.  Having the shell
in my chroot kinda defeats part of why I chrooted in the first place.

I upgraded to 7.2.1, hoping this routine was changed, but it hasn't.

While, IMHO, the safest way to do this would be to code the cp and rm code
internally, I have patched my copy to do a fork and execl to call the cp
and rm programs directly (and placed /bin/cp and /bin/rm in the chroot
jail) as a quick fix... I feel it gives a bit more security.

Can anyone tell me if there is any inherently bad side effects to this?
Or why the "system" call is necessary?

                    ----Steve
Stephen Amadei
Dandy.NET!  CTO
Atlantic City, NJ