| From: | Adam Kornick <akornick(at)whgrp(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | backend closing unexpectedly |
| Date: | 2001-08-13 19:42:35 |
| Message-ID: | m3elqfg310.fsf@shrike.local.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Folks,
I have a moderately complex query running on small views (10-30
records) which used to work, but is now dying unexptecedly. The query
is via aolserver, but also creates the same response when using pgsql.
Within pgsql, I get:
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
Within aolserver, I get:
Error: dbinit: error(localhost::acs,pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
I'm running postgresql-7.1.2-5PGDG, on RedHat 7.1...thoughts?
Thanks,
Adam
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Allan Engelhardt | 2001-08-13 20:00:42 | VACUUM on database with open transaction returns error? |
| Previous Message | Hans-Jürgen Schönig | 2001-08-13 19:23:40 | Get amount of memory allocated by a backend |