Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZSRZY-0006NQ-V6 for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 20 Aug 2015 15:16:09 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZSRZY-00080G-H1 for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 20 Aug 2015 15:16:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZSQzS-0008UL-Ly for pgsql-pkg-yum@postgresql.org; Thu, 20 Aug 2015 14:38:50 +0000 Received: from mail-oi0-x233.google.com ([2607:f8b0:4003:c06::233]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZSQzP-0004xn-Qn for pgsql-pkg-yum@postgresql.org; Thu, 20 Aug 2015 14:38:50 +0000 Received: by oiev193 with SMTP id v193so23805975oie.3 for ; Thu, 20 Aug 2015 07:38:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=WuyXMkQMp4GCFAkkDlbBWFkpSsapnvdXMyEKwsBUWd4=; b=gIOIobeE9nkivYrC410mkBz9nSq2SYNLWM/6h0H1hjpRTiKSF/n+wDTo9gL/C87IKC Cd9Ew3m8jckJJSGpBbB5oOKlM+LqkInvClk2TxXV2BsB3CyH8TPGj1PwxuZeaHT+DUfv U+aBxIioDFZtcdzfbVz72a/Pymj/vIVSln6Q89AMFhlsqJEh4nXShlxgryxW5EO7KZiL 6GIE3RO6qO7tc8MVTFZD6HPggKoStyi+eX3v4cke9RJ/Jc8Z8UZh7Y32Ow5VCH/DW1Ew IFKi2ljIXIbSeMGAY7EDOY92gLlb7bv0sCulheVb20QjLUuJWhAV4uuZC4eydwuVTRdD bWNQ== X-Received: by 10.202.176.139 with SMTP id z133mr2827223oie.105.1440081526034; Thu, 20 Aug 2015 07:38:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.137.9 with HTTP; Thu, 20 Aug 2015 07:38:06 -0700 (PDT) In-Reply-To: <38DF2A7A-4E10-40D7-9194-962C167D798C@pgexperts.com> References: <38DF2A7A-4E10-40D7-9194-962C167D798C@pgexperts.com> From: Hima Mahi Date: Thu, 20 Aug 2015 20:08:06 +0530 Message-ID: Subject: Re: Issue with postgresql-9.4 init.d script To: Jeff Frost Cc: pgsql-pkg-yum@postgresql.org Content-Type: multipart/alternative; boundary=001a113d5f46ce98be051dbf1bc0 X-Pg-Spam-Score: -2.4 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-pkg-yum Precedence: bulk Sender: pgsql-pkg-yum-owner@postgresql.org --001a113d5f46ce98be051dbf1bc0 Content-Type: text/plain; charset=UTF-8 The issue is if some other application has set PGPORT in environment variable, it reads that. It doesn't check the port mentioned in postgresql.conf. For example in my case, We have PostgresPlus advanced server setup on some port and this variable is set. Now , postgresql 9.4 is reading that variable and not the port mentioned in postgresql.conf. Thus , server start fails. On Thu, Aug 20, 2015 at 8:04 PM, Jeff Frost wrote: > > On Aug 20, 2015, at 4:06 AM, Hima Mahi wrote: > > Earlier in 9.2 version, init.d script was exporting and using PGPORT for > db server start. In 9.4 that option has been removed. It creates issue in > case if some other PGPORT variable is set to some value. Then it uses thats > value and fails to start. > > > I think our opinion with that change was that people should be setting the > port in the postgresql.conf file. > > --001a113d5f46ce98be051dbf1bc0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The issue is if some other application has set PGPORT in e= nvironment variable, it reads that. It doesn't check the port mentioned= in postgresql.conf.=C2=A0
For example in my case, We have PostgresPlus= advanced server setup on some port and this variable is set. Now , postgre= sql 9.4 is reading that variable and not the port mentioned in postgresql.c= onf. Thus , server start fails.

<= div class=3D"gmail_quote">On Thu, Aug 20, 2015 at 8:04 PM, Jeff Frost <je= ff@pgexperts.com> wrote:

On Aug 20, 2015, at 4:06 AM, Hima Mahi <himamahi09@gmail.com> wrot= e:

Earlier in 9.2 version, init.d script was exporting and = using PGPORT for db server start. In 9.4 that option has been removed. It c= reates issue in case if some other PGPORT variable is set to some value. Th= en it uses thats value and fails to start.

I think our opinion with that change was that people s= hould be setting the port in the postgresql.conf file.

=
--001a113d5f46ce98be051dbf1bc0--