Re: persistent 'psql: FATAL: "listen_addresses" cannot be changed after server start

From: "David Rovner" <DRovner(at)princetonservergroup(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Steve Crawford" <scrawford(at)pinpointresearch(dot)com>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: persistent 'psql: FATAL: "listen_addresses" cannot be changed after server start
Date: 2007-10-10 14:11:27
Message-ID: F543E86A0B415E41806A68AA76E3C7F401A0FE7F@mailman.teve.inc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Wednesday, October 10, 2007 10:02 AM
> To: David Rovner
> Cc: Steve Crawford; pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] persistent 'psql: FATAL: "listen_addresses"
cannot be
> changed after server start
>
> "David Rovner" <DRovner(at)princetonservergroup(dot)com> writes:
> > I see this error at the command prompt in root executing anything
that
> > starts with "psql". The argument list does not matter. "psql" with
no
> > arguments returns this error as well.
>
> PGOPTIONS environment variable, perhaps? It's hard to imagine why
> anyone would try to set listen_addresses that way, but ...
>
> $ PGOPTIONS='--listen_addresses=*' psql
> psql: FATAL: parameter "listen_addresses" cannot be changed after
server
> start
> $
> regards, tom lane

Perhaps if I knew what conditions cause the "psql" call to report the
error no matter what arguments are listed, that might lead to an answer.
Is there a hidden file or entry in a config file that forces this
condition with postgres running?

Dave

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2007-10-10 14:56:53 Re: persistent 'psql: FATAL: "listen_addresses" cannot be changed after server start
Previous Message David Rovner 2007-10-10 14:09:16 Re: persistent 'psql: FATAL: "listen_addresses" cannot be changed after server start