Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZSRZ3-0006Me-Dw for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 20 Aug 2015 15:15:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZSRZ2-0007wq-Ld for pgsql-pkg-yum@arkaria.postgresql.org; Thu, 20 Aug 2015 15:15:36 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZSRLs-0007dc-Be for pgsql-pkg-yum@postgresql.org; Thu, 20 Aug 2015 15:02:00 +0000 Received: from mail-oi0-x22f.google.com ([2607:f8b0:4003:c06::22f]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZSRLo-00047G-TE for pgsql-pkg-yum@postgresql.org; Thu, 20 Aug 2015 15:01:59 +0000 Received: by oiev193 with SMTP id v193so24263922oie.3 for ; Thu, 20 Aug 2015 08:01:56 -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=Wg9NAqeWA0+nYDW0mtEDButaswTsqWuJbdM/SAL3jTg=; b=sCjtune4yEOUj9QJwC3oeJqPFqVao6qu5p+yyyDT4ucXfH+GMy6SuIsm8BlYxDscrF hxW6LeWxTM8Q3Ko/H9X+Wb1apmONKq8EFYCvxDp1OMysPfi+5AOR9rhjuaAGG+gelxwq zPvndI++grXk1PcmowhrNxT5ya3GilDLpqNgczq8bnKf131eQWpujNdljqxZHnwE2YlQ 683KEBGgx9h4drPJirscr+XAC322t1rv86UD6lMfRbp7/GVyoJTNA2f5rkwi2uUbHIVb dH3bO9gSGW7nwySnRa1RSffy/kCp4p2gJ1kVH3bmr1RoX+EIE4IXJyMTM3OtUuSRYy7e HK0g== X-Received: by 10.202.104.164 with SMTP id o36mr2964426oik.57.1440082915987; Thu, 20 Aug 2015 08:01:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.137.9 with HTTP; Thu, 20 Aug 2015 08:01:16 -0700 (PDT) In-Reply-To: References: <38DF2A7A-4E10-40D7-9194-962C167D798C@pgexperts.com> From: Hima Mahi Date: Thu, 20 Aug 2015 20:31:16 +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=001a1140fcc8a79d57051dbf6e70 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 --001a1140fcc8a79d57051dbf6e70 Content-Type: text/plain; charset=UTF-8 Hi, Please avoid my last mail. The port was commented in postgresql.conf, that's why it was not picking from there. On uncommenting it , its overriding PGPORT and working fine. On Thu, Aug 20, 2015 at 8:08 PM, Hima Mahi wrote: > 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. >> >> > --001a1140fcc8a79d57051dbf6e70 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

Please avoid my last mail. The port= was commented in postgresql.conf, that's why it was not picking from t= here. On uncommenting it , its overriding PGPORT and working fine.

On Thu, Aug 20= , 2015 at 8:08 PM, Hima Mahi <himamahi09@gmail.com> wrote= :
The issue is if some o= ther application has set PGPORT in environment variable, it reads that. It = doesn't check the port mentioned in postgresql.conf.=C2=A0
For exam= ple 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 no= t the port mentioned in postgresql.conf. Thus , server start fails.

=
On Thu, Aug 20, 2015 at 8:04 PM, Jeff Frost <j= eff@pgexperts.com> wrote:
<= div style=3D"word-wrap:break-word">

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

Earlier in 9.2 version, init.d script was exporting and using PGPO= RT for db server start. In 9.4 that option has been removed. It creates iss= ue 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 s= etting the port in the postgresql.conf file.



--001a1140fcc8a79d57051dbf6e70--