"Eric G. Miller" <egm2@jps.net> writes:
> And have you checked your postgres.log?
I forgot about the log. Anyhow, I can not see from it how to correct
the situation:
---------------------------------
pq_recvbuf: unexpected EOF on client connection
Smart Shutdown request at Thu Jun 28 08:34:56 2001
Server process (pid 12898) exited with status 512 at Thu Jun 28 17:14:09 2001
Terminating any active server processes...
Server processes were terminated at Thu Jun 28 17:14:09 2001
Reinitializing shared memory and semaphores
The Data Base System is starting up
The Data Base System is starting up
The Data Base System is starting up
/usr/lib/postgresql/bin/postmaster: Startup proc 12953 exited with status 512 -
abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13036 exited with status 512 -
abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13098 exited with status 512 -
abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13138 exited with status 512 -
abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13671 exited with status 512 -
abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13859 exited with status 512 -
abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13892 exited with status 512 -
abort
/usr/lib/postgresql/bin/postmaster: Startup proc 14034 exited with status 512 -
abort
------------------------------------------------
Fortunately the data is not that critical. There were about 430000
records in a table inserted from ftplogs by a script. I could have
tried removing postgresql and reinstall it, but that would be avoiding
the real problem - and it feels too much like the windows way of
doing.
Johann
--
Johann Spies
Informasietegnologie
Universiteit van Stellenbosch
"One thing have I desired of the LORD, that will I seek
after; that I may dwell in the house of the LORD all
the days of my life, to behold the beauty of the LORD,
and to inquire in his temple."
Psalms 27:4
