No title

Teruel Tony wrote:

Hi,

I'm having this message when trying to perform
a query.. someone knows what do I have to do to
fix it?

Thanks

pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
We have lost the connection to the backend, so further processing is
impossible. Terminating.

Have an excellent day
teruel@excite.com
Mexico

Please post the query, the definition of the tables the query is
accessing and the version of PostgreSQL you are using. You are
tickling a bug. That message means the backend crashed while
executing your query. Right off hand I would sugguest testing the
same query with 7.0RC1 from ftp.postgresql.org to see if the
error still exists in the about-to-be newest release.

Hope that helps,

Mike Mascari

Teruel Tony wrote:

I'm having this message when trying to perform
a query.. someone knows what do I have to do to
fix it?

pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
We have lost the connection to the backend, so further processing is
impossible. Terminating.

What is the query? What version of pgsql? What does your server log say?

Regards,
Ed Loehr

Hi,

The query is simple:

select count(*) from table;

I have the same error message with almost all queries,
I'm trying to debug what's new on that table (data)
because it was working fine..

The version I'm using:

PostgreSQL 6.5.3 on i586-pc-linux-gnu, compiled by gcc egcs-2.91.66

The table:

+----------------------------+----------------------------+------+
|           Field            |           Type             |Length|
+----------------------------+----------------------------+------+
| dfoclave                   | int4 not null              |    4 |
| dfoforo                    | int4 not null              |    4 |
| dfopadre                   | int4                       |    4 |
| dfonombre                  | varchar()                  |   80 |
| dfotitulo                  | varchar()                  |   80 |
| dfofecha                   | timestamp not null         |    4 |
| dfotexto                   | text                       |  var |
+----------------------------+----------------------------+------+

On Tue, 25 Apr 2000 15:20:55 -0400, Mike Mascari wrote:

Please post the query, the definition of the tables the query is
accessing and the version of PostgreSQL you are using. You are
tickling a bug. That message means the backend crashed while
executing your query. Right off hand I would sugguest testing the
same query with 7.0RC1 from ftp.postgresql.org to see if the
error still exists in the about-to-be newest release.
Hope that helps,
Mike Mascari

Have an excellent day
teruel@excite.com
Mexico

_______________________________________________________
Get 100% FREE Internet Access powered by Excite
Visit http://freelane.excite.com/freeisp

Teruel Tony wrote:

Hi,

The query is simple:

select count(*) from table;

I have the same error message with almost all queries,
I'm trying to debug what's new on that table (data)
because it was working fine..

The version I'm using:

PostgreSQL 6.5.3 on i586-pc-linux-gnu, compiled by gcc egcs-2.91.66

The table:

+----------------------------+----------------------------+------+
|           Field            |           Type             |Length|
+----------------------------+----------------------------+------+
| dfoclave                   | int4 not null              |    4 |
| dfoforo                    | int4 not null              |    4 |
| dfopadre                   | int4                       |    4 |
| dfonombre                  | varchar()                  |   80 |
| dfotitulo                  | varchar()                  |   80 |
| dfofecha                   | timestamp not null         |    4 |
| dfotexto                   | text                       |  var |
+----------------------------+----------------------------+------+

Just a wild shot, of course - but perhaps an index or relation
file is corrupted. Unless the table is unusually large, I don't
see how the backend could die on this one. Perhaps you could
peform a manual COPY, drop and recreate the table and its indexes
and COPY the data back in.

Hope that helps,

Mike Mascari

I had this same problem after a user had cntrl^Z quit from psql several
times in the middle of queries. He then performed a vacuum which locked it
up further. After I removed the lock file I could not perform even the
simplest queries. The only way I fixed it was to drop the db and restore it
from a previous pd_dump.