Re: Performance of subselects

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
Cc: Christian Schröder <cs(at)deriva(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Performance of subselects
Date: 2009-03-08 19:15:28
Message-ID: dcc563d10903081215q5582d8dhd6ce499c8cbca302@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Mar 8, 2009 at 12:47 PM, Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> wrote:
> work_mem constraints amount of memory allocated per connection, hence

Actually, it's per sort. And there can be > 1 sort per query.

> you can run out of memory if too many connections try to use too much
> of it at the same time, that's why it is advisable to set work_mem per
> connection/query, should the connection/query require more.

Definitely.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2009-03-08 19:29:07 Re: Enable user access from remote host
Previous Message V S P 2009-03-08 19:01:17 Re: [Q] Cluster design for geographically separated dbs