public inbox for [email protected]
help / color / mirror / Atom feedIssue with postgresql-9.4 init.d script
5+ messages / 3 participants
[nested] [flat]
* Issue with postgresql-9.4 init.d script
@ 2015-08-20 11:06 Hima Mahi <[email protected]>
2015-08-20 14:34 ` Re: Issue with postgresql-9.4 init.d script Jeff Frost <[email protected]>
0 siblings, 1 reply; 5+ messages in thread
From: Hima Mahi @ 2015-08-20 11:06 UTC (permalink / raw)
To: pgsql-pkg-yum
Hi,
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.
Regards,
Himanchali.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Issue with postgresql-9.4 init.d script
2015-08-20 11:06 Issue with postgresql-9.4 init.d script Hima Mahi <[email protected]>
@ 2015-08-20 14:34 ` Jeff Frost <[email protected]>
2015-08-20 14:38 ` Re: Issue with postgresql-9.4 init.d script Hima Mahi <[email protected]>
0 siblings, 1 reply; 5+ messages in thread
From: Jeff Frost @ 2015-08-20 14:34 UTC (permalink / raw)
To: Hima Mahi <[email protected]>; +Cc: pgsql-pkg-yum
>
> On Aug 20, 2015, at 4:06 AM, Hima Mahi <[email protected]> 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.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Issue with postgresql-9.4 init.d script
2015-08-20 11:06 Issue with postgresql-9.4 init.d script Hima Mahi <[email protected]>
2015-08-20 14:34 ` Re: Issue with postgresql-9.4 init.d script Jeff Frost <[email protected]>
@ 2015-08-20 14:38 ` Hima Mahi <[email protected]>
2015-08-20 15:01 ` Re: Issue with postgresql-9.4 init.d script Hima Mahi <[email protected]>
2015-08-26 10:11 ` Re: Issue with postgresql-9.4 init.d script Devrim GÜNDÜZ <[email protected]>
0 siblings, 2 replies; 5+ messages in thread
From: Hima Mahi @ 2015-08-20 14:38 UTC (permalink / raw)
To: Jeff Frost <[email protected]>; +Cc: pgsql-pkg-yum
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 <[email protected]> wrote:
>
> On Aug 20, 2015, at 4:06 AM, Hima Mahi <[email protected]> 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.
>
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Issue with postgresql-9.4 init.d script
2015-08-20 11:06 Issue with postgresql-9.4 init.d script Hima Mahi <[email protected]>
2015-08-20 14:34 ` Re: Issue with postgresql-9.4 init.d script Jeff Frost <[email protected]>
2015-08-20 14:38 ` Re: Issue with postgresql-9.4 init.d script Hima Mahi <[email protected]>
@ 2015-08-20 15:01 ` Hima Mahi <[email protected]>
1 sibling, 0 replies; 5+ messages in thread
From: Hima Mahi @ 2015-08-20 15:01 UTC (permalink / raw)
To: Jeff Frost <[email protected]>; +Cc: pgsql-pkg-yum
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 <[email protected]> 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 <[email protected]> wrote:
>
>>
>> On Aug 20, 2015, at 4:06 AM, Hima Mahi <[email protected]> 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.
>>
>>
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Issue with postgresql-9.4 init.d script
2015-08-20 11:06 Issue with postgresql-9.4 init.d script Hima Mahi <[email protected]>
2015-08-20 14:34 ` Re: Issue with postgresql-9.4 init.d script Jeff Frost <[email protected]>
2015-08-20 14:38 ` Re: Issue with postgresql-9.4 init.d script Hima Mahi <[email protected]>
@ 2015-08-26 10:11 ` Devrim GÜNDÜZ <[email protected]>
1 sibling, 0 replies; 5+ messages in thread
From: Devrim GÜNDÜZ @ 2015-08-26 10:11 UTC (permalink / raw)
To: Hima Mahi <[email protected]>; Jeff Frost <[email protected]>; +Cc: pgsql-pkg-yum
Hi,
On Thu, 2015-08-20 at 20:08 +0530, 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.
That is EDB's preference over packaging. We removed that intentionally,
because people had to change in two places at some point.
So just change the port in postgresql.conf -- that is all.
Regards,
--
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
--
Sent via pgsql-pkg-yum mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pkg-yum
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2015-08-26 10:11 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2015-08-20 11:06 Issue with postgresql-9.4 init.d script Hima Mahi <[email protected]>
2015-08-20 14:34 ` Jeff Frost <[email protected]>
2015-08-20 14:38 ` Hima Mahi <[email protected]>
2015-08-20 15:01 ` Hima Mahi <[email protected]>
2015-08-26 10:11 ` Devrim GÜNDÜZ <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox