On 5/27/02 4:18 PM, "Doug Fields" <dfields-pg-general@pexicom.com> wrote:
>
>> 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.
>> You are currently not connected to a database.
>
> I had this happen to me the other day, when my server booted with only 1GB
> of RAM instead of the usual 2GB. PostgreSQL started thrashing something
> fierce since I give it 1.4GB of shared memory, and not too long after that
> I got that same message in a JDBC SQLException.
>
> That doesn't really help, but...
>
> Doug
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
That's a pretty standard "PostgreSQL did something bad" message, so without
more information it's hard to know what happened... Can you replicate this
crash?
-Mitch