psql crashing - don't know why

From: "Brent Wood" <b(dot)wood(at)niwa(dot)co(dot)nz>
To: <pgsql-general(at)postgresql(dot)org>
Subject: psql crashing - don't know why
Date: 2009-08-09 23:04:24
Message-ID: 4A7FFEB90200007B0001D600@gwia1.ham.niwa.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi...

I have a view across 3 tables, total some 5m rows.

I can extract parts of the view, entire rows, with a where clause
(eg: select * from view where cell_id=100000;)

If I try to select the entire view (eg: select * from view;) it runs for a while then gives the error msg "Killed" and returns to the system prompt, having exited psql.

The log says:
2009-08-10 00:19:01 NZST ben200601 woodb LOG: could not send data to client: Broken pipe
2009-08-10 00:19:48 NZST ben200601 woodb LOG: unexpected EOF on client connection

I have written a script along the lines of:

get distinct cell_id from table; > file

while read cell ; do
psql -d db -c "select * from view where cell=$cell;" >> output
done < file

This worked, & the number of lines in the output file is the same number as that returned by "select count(*) from view;" (which works fine), but I'd like to find out the cause of the error. I assume there is some sort of timeout or overflow occurring, but I can't see any indication of what settings I can change to fix this. All the underlying tables have just had vacuum analyse run on them.

I'm running PostgreSQL 8.1.4 on x86_64 Linux, I know it is dated, but I'm not in a position to upgrade at this point.

Thanks,

Brent Wood

Brent Wood
DBA/GIS consultant
NIWA, Wellington
New Zealand
NIWA is the trading name of the National Institute of Water & Atmospheric Research Ltd.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2009-08-09 23:10:07 Re: psql crashing - don't know why
Previous Message Kobus Wolvaardt 2009-08-09 22:41:31 Re: Postgres memory question