> -----Original Message----- > From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx] > Sent: Wednesday, October 10, 2007 10:02 AM > To: David Rovner > Cc: Steve Crawford; pgsql-admin@xxxxxxxxxxxxxx > Subject: Re: persistent 'psql: FATAL: "listen_addresses" cannot be > changed after server start > > "David Rovner" <DRovner@xxxxxxxxxxxxxxxxxxxxxxxx> 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 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
