On Fri, Jul 16, 2010 at 4:31 PM, Patric Michael <bluestar43@xxxxxxxxx> wrote: > Hi all... > > I joined this list in an effort to solve a puzzle I fail to understand. > Thank you in advance for taking the time to read. > > I've been managing a domain for the last eight years as an erstwhile > administrator. Erstwhile meaning it is largely a matter of setting up and > automating the routine functions of the machine. I am not by any stretch of > the imagination a guru. And please keep in mind that aside from minor tweaks > and upgrades, I pretty much leave the machine alone. > > In that time, I've upgraded postgres 7.1 to 7.4 and now to 8.1 and have > rarely needed to reboot the machine. (Yay CentOS!) Manual installs from > source. Not RPM's > > A few days ago however, the co-lo appears to have taken the system down for > a short time and brought it back up, essentially rebooting the system. No > big deal, except that until then, it had been running for almost two years. > > Everything came back up as expected, with the exception of postgres. When I > went to start it manually, I got an error warning of an unrecognized > tcpip_socket parameter in postgresql.conf. Searching the 8.1 manual I > discovered it had been deprecated in favor of listen_addresses. Odd, but > okay. Is it possible you started 8.1 in a different directory by hand (pg_ctl -D /my/other/dir start) many years ago and that the default old install of 7.4 is sitting in the /var/lib/pgsql spot? -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
