Re: sort_mem param of postgresql.conf

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: "Greg Smith" <gsmith(at)gregsmith(dot)com>
Cc: "pgSQL - General" <pgsql-general(at)postgresql(dot)org>
Subject: Re: sort_mem param of postgresql.conf
Date: 2008-11-13 14:59:34
Message-ID: 2f4958ff0811130659k4b938c6era88626205845b960@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 12, 2008 at 11:08 PM, Greg Smith <gsmith(at)gregsmith(dot)com> wrote:

> Be advised that the work_mem setting (and its deprecated alias sort_mem)
> are on a per-client basis. So if you have a bunch of people running reports
> with that setting, you might discover your server running out of memory;
> that's a really high setting. Generally, if it's only a report or two that
> need a lot more working memory for sorts, you can do this at the beginning
> of them instead:
>
> set work_mem='512MB';
>
so how do I change it back to default (without knowing what the previous val
was). I suppose having it in a transaction won't do :P

--
GJ

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-11-13 15:06:05 Re: [GENERAL] db_user_namespace, md5 and changing passwords
Previous Message Magnus Hagander 2008-11-13 14:48:17 Re: [GENERAL] db_user_namespace, md5 and changing passwords