Skip site navigation (1) Skip section navigation (2)

Re: Rapidly finding maximal rows

From: James Cranch <jdc41(at)cam(dot)ac(dot)uk>
To: pgsql-performance(at)postgresql(dot)org
Cc: bricklen <bricklen(at)gmail(dot)com>
Subject: Re: Rapidly finding maximal rows
Date: 2011-10-12 11:41:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Dear Bricklen,

>Try setting work_mem to something larger, like 40MB to do that sort
>step in memory, rather than spilling to disk. The usual caveats apply
>though, like if you have many users/queries performing sorts or
>aggregations, up to that amount of work_mem may be used at each step
>potentially resulting in your system running out of memory/OOM etc.

Thanks, I'll bear that in mind as a strategy. It's good to know. But since 
Dave has saved me the sort altogether, I'll go with his plan.

Best wishes,


James Cranch       

In response to

pgsql-performance by date

Next:From: Vishnu S.Date: 2011-10-13 12:52:32
Subject: Tablespace files deleted automatically.
Previous:From: James CranchDate: 2011-10-12 11:40:48
Subject: Re: Rapidly finding maximal rows

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group