> netstat=> select count(*) from ruscan_current ; > count > -------- > 194672 > (1 row) > > netstat=> select count(sld_id) from ruscan_current ; > server closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > The connection to the server was lost. Attempting reset: Failed. > !> > > That's All ! > > And there are no log messages with this configureation of logging : > > server_min_messages = info > client_min_messages = info > > There are only the following in logs : > > Mar 29 13:20:19 frost postgres[14486]: [7] LOG: server process (pid 15079) was > terminated by signal 11
Unless your ulimits are set up to disallow core files, this should have generated a core file in the data directory for the database you were connected to. If you have one, please post a backtrace. If not, set the ulimits to allow core, restart the server and see if you can get it to crash again with a core. ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
