Re: pg_ctl restart bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: jmitchell(at)greatbridge(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_ctl restart bug
Date: 2001-04-20 20:25:09
Message-ID: 28068.987798309@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

pg_ctl restart works fine with this patch, but I'm not sure whether it
breaks useful cases for the other paths:

***************
*** 323,335 ****
shift
po_path=$1
shift
! POSTOPTS=$@
fi
else # -o given
POSTOPTS="-D $PGDATA $POSTOPTS"
fi

! eval '$po_path' '$POSTOPTS' $logopt '&'

# if had an old lockfile, check to see if we were able to start
if [ -n "$oldpid" ];then
--- 323,335 ----
shift
po_path=$1
shift
! POSTOPTS="$@"
fi
else # -o given
POSTOPTS="-D $PGDATA $POSTOPTS"
fi

! eval '$po_path' $POSTOPTS $logopt '&'

# if had an old lockfile, check to see if we were able to start
if [ -n "$oldpid" ];then

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2001-04-20 20:27:43 Re: the operator "=" does not work for some SQL queries
Previous Message Tom Lane 2001-04-20 20:00:36 Re: pg_ctl restart bug