Re: capturing/viewing sort_mem utilization on a per query basis - Mailing list pgsql-general

From Tom Lane
Subject Re: capturing/viewing sort_mem utilization on a per query basis
Date
Msg-id 1094.1107370033@sss.pgh.pa.us
Whole thread Raw
In response to Re: capturing/viewing sort_mem utilization on a per query basis  (Lonni J Friedman <netllama@gmail.com>)
List pgsql-general
Lonni J Friedman <netllama@gmail.com> writes:
> OK, i think i see what you're requesting.  How's this:

What about field_value, does it in fact have circa 34444 rows?

These tables are surely nowhere near big enough to bloat a hash table to
upwards of 2Gb, as your log shows happened.  I'm thinking that you must
have found some sort of bug, or memory leak maybe.  Is there a way I can
get access to your data set to trace through the behavior with a debugger?

(We should probably take the discussion offlist at this point.)

            regards, tom lane

pgsql-general by date:

Previous
From: Bricklen Anderson
Date:
Subject: Re: Invalid headers and xlog flush failures
Next
From: Tom Lane
Date:
Subject: Re: plpython.so