Re: capturing/viewing sort_mem utilization on a per query basis

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lonni J Friedman <netllama(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: capturing/viewing sort_mem utilization on a per query basis
Date: 2005-02-02 17:13:59
Message-ID: 29801.1107364439@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Lonni J Friedman <netllama(at)gmail(dot)com> writes:
> Although, looking in the log postgresql is generating, I'm seeing the
> following at the same time as that OOM above so it certainly looks
> like the DB is barfing:

OK, then it's a backend issue not a client-side issue.

> HashBatchContext: -1934683632 total in 295 blocks; 135760 free (879
> chunks); -1934819392 used

Hmm, looks like a hash join ran out of memory. What PG version is this
again, and what do you have sort_mem set to? Can you show an EXPLAIN
for the query that is failing like this?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bricklen Anderson 2005-02-02 17:17:08 Re: Invalid headers and xlog flush failures
Previous Message Lonni J Friedman 2005-02-02 17:10:59 Re: capturing/viewing sort_mem utilization on a per query basis