Re: BUG #6074: postgresql service script

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Tomas Enrique Cardozo Baudry <tomas(dot)enrique(dot)cardozo(dot)baudry(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6074: postgresql service script
Date: 2011-06-23 03:35:37
Message-ID: 4E02B489.6070104@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 22/06/11 20:47, Tomas Enrique Cardozo Baudry wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6074
> Logged by: Tomas Enrique Cardozo Baudry
> Email address: tomas(dot)enrique(dot)cardozo(dot)baudry(at)gmail(dot)com
> PostgreSQL version: 8.4.4
> Operating system: Centos 5.6
> Description: postgresql service script
> Details:
>
> configuring the posgresql.conf on another port the service doesnt load the
> port variable, because in the postgresql service script is a variable PGPORT
> and this rewrite the configuration variable

I'm pretty sure that init script is part of CentOS (probably really part
of Red Hat Enterprise Linux), not part of PostgreSQL.

The script should *not* respect values from the environment; it's a good
thing that it doesn't. Otherwise setting PGPORT to tell psql what to do
would as a side effect change what port the server listened on if you
restarted it from that shell!

What the script should do is get those settings from /etc/sysconfig or
/etc/default (dunno which CentOS uses) so you don't have to hack the
init script directly.

--
Craig Ringer

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-06-23 03:52:13 Re: BUG #6074: postgresql service script
Previous Message Roman 2011-06-22 22:35:28 BUG #6075: mergejoin early termination estimates bug or defficiency