Re: pg_ctl restart bug - Mailing list pgsql-bugs

From Tom Lane
Subject Re: pg_ctl restart bug
Date
Msg-id 28068.987798309@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_ctl restart bug  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pg_ctl restart bug
Re: pg_ctl restart bug
Re: pg_ctl restart bug
List 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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_ctl restart bug
Next
From: Tom Lane
Date:
Subject: Re: the operator "=" does not work for some SQL queries