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

Поиск
Список
Период
Сортировка
От David Rovner
Тема Re: persistent 'psql: FATAL: "listen_addresses" cannot be changed after server start
Дата
Msg-id F543E86A0B415E41806A68AA76E3C7F401A0FE7F@mailman.teve.inc
обсуждение исходный текст
Ответ на Re: persistent 'psql: FATAL: "listen_addresses" cannot be changed after server start  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-admin
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Wednesday, October 10, 2007 10:02 AM
> To: David Rovner
> Cc: Steve Crawford; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] persistent 'psql: FATAL: "listen_addresses"
cannot be
> changed after server start
>
> "David Rovner" <DRovner@princetonservergroup.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

В списке pgsql-admin по дате отправления:

Предыдущее
От: "David Rovner"
Дата:
Сообщение: Re: persistent 'psql: FATAL: "listen_addresses" cannot be changed after server start
Следующее
От: Tom Lane
Дата:
Сообщение: Re: persistent 'psql: FATAL: "listen_addresses" cannot be changed after server start