Re: backend crashes with mnogosearch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nick Wellnhofer <nick(at)paradigmashift(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: backend crashes with mnogosearch
Date: 2001-04-13 16:11:31
Message-ID: 4256.987178291@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Nick Wellnhofer <nick(at)paradigmashift(dot)com> writes:
> further investigatoin showed that a simple "SELECT * FROM url" query
> resulted in

> Backend message type 0x44 arrived while idle
> pqReadData() -- backend closed the channel unexpectedly.

Are you sure this is a backend crash? (Real proof would be a report
of abnormal child termination in the postmaster's log, or appearance
of a core dump file in the database's subdirectory.) The "arrived while
idle" bit looks suspiciously like the sort of misbehavior that libpq
tends to engage in if it runs out of memory for a query result.

> then i tried several "SELECT * FROM url LIMIT <some number>" queries.
> up to a certain number the queries were successful, but from that
> number on i got the error message.

How big is the "certain number", and how close might that number of
rows come to exhausting your frontend application's available memory?

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2001-04-13 17:20:31 Re: aliasing table name in update
Previous Message Tom Lane 2001-04-13 16:06:26 Re: runtest bug and bigcheck problems