> > No help here, but a request:
> > Could we have an option to do the fork()/exec() the old way as well as the
> > new sleek fork() only. I want to do some performance testing under gprof and
> > want to be able to replace my postgres binary with a shell script to save
> > the gmon.out file eg:
> > #!/bin/sh
> > postgres.bin $*
> > mv gmon.out gmon.$$
> > This won't work unless and exec() is done.
> I am confused. What doesn't work without the exec()?
Replacing the postgres binary with a shell script that executes the real
postgres binary and then moves the gmon.out file out of the way.
$ mv postgres postgres.bin
$cat > postgres
mv gmon.out gmon.$$
$ postmaster ...
$ psql template1
David Gould dg(at)illustra(dot)com 510.628.3783 or 510.305.9468
Informix Software 300 Lakeside Drive Oakland, CA 94612
- A child of five could understand this! Fetch me a child of five.
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 1998-06-23 18:38:02|
|Subject: Re: [HACKERS] I thought we had fixed this for v6.3.2 ...?|
|Previous:||From: The Hermit Hacker||Date: 1998-06-23 18:10:29|
|Subject: I thought we had fixed this for v6.3.2 ...?|