Sorry - that semicolon is an artifact of a change I made - I attempted
to put
postmaster_pid=$! inside the executing statement, but as I discovered,
if you put it before last &, you
get the backgrounded process before postmaster.
I'm presently checking out how the SLES init scripts work, but a
Eric E <[EMAIL PROTECTED]> writes:
> I chased the problem down to the following lines in pg_regress:
>"$bindir/postmaster" -D "$PGDATA" -F $postmaster_options
>> "$LOGDIR/postmaster.log"; 2>&1 &
^
Is there really a semicolon there? There should not be (and
Hi all,
I'm trying to run pg_regress as part of a build of Postgres 8.1 on
Suse Linux Enterprise Server 9. I keep getting the following error:
./pg_regress: line 264: kill: (25049) - No such process
I chased the problem down to the following lines in pg_regress:
"$bindir/postmaster" -D "$P
