From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
---|---|
To: | David Rovner <DRovner(at)princetonservergroup(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: persistent 'psql: FATAL: "listen_addresses" cannot be changed after server start |
Date: | 2007-10-09 22:08:02 |
Message-ID: | 470BFBC2.4070003@pinpointresearch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
David Rovner wrote:
>...
> After some network configuration changes (IP changes and some editing to
> config files which may have been interrupted buy shutdowns), I cannot
> get past this error:
That's a bit vague. What changed externally with your network? What
files were you changing and what were you changing in them? What do you
mean by "may have been interrupted buy shutdowns" - were the changes
made or not? Did you restart the server and was it a full reboot or just
postgresql?
> 'psql: FATAL: "listen_addresses" cannot be changed after server start
Where do you see this error? The statement is true - listen addresses is
a parameter that can only be set when the PostgreSQL server starts.
Trying to change the parameter from, say, psql by running
"set listen_addresses to '*';" will yield this error. Could there be a
script that generates such a command?
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Trutwin | 2007-10-10 02:54:09 | Re: Schema objects |
Previous Message | David Rovner | 2007-10-09 21:29:32 | persistent 'psql: FATAL: "listen_addresses" cannot be changed after server start |