On Wed, 28 Feb 2007, Alan Hodgson wrote:
Something happened to your /tmp directory after PostgreSQL started up.
Alan, Seems so, doesn't it?
Stop the postmaster, clean out the socket in /tmp, and restart the postmaster, and it will likely fix it up. Then you can investigate your boot process to see what's going wrong.
Ahhh-h-h! That did it. I did not realize that I could kill the socket and have postgresql start it again upon loading. It's there now (owned by postgres.users), and I can access both the shell and my accounts via SQL-Ledger. Thanks very much, Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 ---------------------------(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
