[GENERAL] pqReadData() -- backend closed the channel unexpectedly.

2001-07-23 Thread Lee Harr
I am running PostgreSQL 7.1.2 on FreeBSD 4.3 This is an old 486 with only 12MB memory. I am able to create databases and insert and retrieve data, but when I try to query on the structure of the database I am getting this error: signin=# \d person_personid_seq pqReadData() -- backend closed the

Re: [GENERAL] pqReadData() -- backend closed the channel unexpectedly (huh?)

2000-11-07 Thread Tom Lane
Frank Miles <[EMAIL PROTECTED]> writes: > query: delete from units where unit_id = 5; > ProcessQuery > /opt/pgsql/bin/postmaster: reaping dead processes... > /opt/pgsql/bin/postmaster: CleanupProc: pid 21004 exited with status 139 > Server process (pid 21004) exited w

[GENERAL] pqReadData() -- backend closed the channel unexpectedly (huh?)

2000-11-07 Thread Frank Miles
Hello all: I have a simple database which is now exhibiting some strange symptoms. The most obviously sick is where I try to delete a record in a table, and get the response: pqReadData() -- backend closed the channel unexpectedly. This probably means the backend

Re: [GENERAL] pqReadData() -- backend closed the channel unexpectedly

2000-09-19 Thread Tom Lane
Buddy Lee Haystack <[EMAIL PROTECTED]> writes: > Here they are, but they seem as vague as the Apache error logs -to me anyway... You're right, not much info there except that a backend died untimely. Unless you had ulimit set to prevent it, the crashing backend should've left a core file in the

Re: [GENERAL] pqReadData() -- backend closed the channel unexpectedly

2000-09-19 Thread Stephan Szabo
> /usr/bin/postmaster: CleanupProc: pid 888 exited with status 139 Okay, we have a postgres process going down with a SEGV. Do you have a core file? I don't quite remember where they end up, but my guess would be either the directory with postgres or somewhere in the data directory (probably t

Re: [GENERAL] pqReadData() -- backend closed the channel unexpectedly

2000-09-19 Thread Buddy Lee Haystack
Thanks for the quick response! Here they are, but they seem as vague as the Apache error logs -to me anyway... FindExec: found "/usr/bin/postgres" using argv[0] /usr/bin/postmaster: BackendStartup: pid 886 user nobody db rzone socket 4 FindExec: found "/usr/bin/postgres" using argv[0] started:

Re: [GENERAL] pqReadData() -- backend closed the channel unexpectedly

2000-09-19 Thread Stephan Szabo
On Tue, 19 Sep 2000, Buddy Lee Haystack wrote: > I'm confused. Where do I need to start looking? The script is fine... Best bet is to start by getting the end of the postmaster logs. That'll probably have more information about immediate causes.

[GENERAL] pqReadData() -- backend closed the channel unexpectedly

2000-09-19 Thread Buddy Lee Haystack
I have been using: *RedHat Linux 6.1 [2.2.12-20] on Intel *PostgreSQL 6.5.3-3 [your RPMs] *Perl 5.00503 *Apache 1.3.9 *mod_perl 1.21 *DBI 1.13 *DBD-Pg-0.93 on 2 Intel systems without any problems for several months now, the production website is an SMP box & the development box is a old, single

[GENERAL] pqReadData() -- backend closed the channel unexpectedly.

1999-02-09 Thread Ludovico Magnocavallo
I have recently installed postgresql 6.4.2 on a Linux 2.2.0 box, and I keep getting this error message when I queue a a few queries in a Perl script: pqReadData() -- backend closed the channel unexpectedly. My script has a loop that performs three queries for every hour of a single day: the firs

RE: [GENERAL] pqReadData() -- backend closed the channel unexpectedly.

1999-02-09 Thread Jackson, DeJuan
1st suggestion - If there is no reason behind have temp tables rewrite your sql to eliminate them (this reduces to just 24 queries): INSERT INTO week (address, origbytes, destbytes, when) SELECT o.origine, sum(o.bytes), sum(d.bytes), '09/02/1999 9:00:01' FROM day o, day d WHERE o.origine=d