Re: SET work_mem = '1TB';

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SET work_mem = '1TB';
Date: 2013-06-18 17:40:24
Message-ID: CA+U5nM+zo+PPBA64VV-i2PNmBxVTLC8JLnjhtiDmUft_V6-q-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18 June 2013 17:10, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Tue, Jun 18, 2013 at 1:06 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>> On Tuesday, May 21, 2013, Simon Riggs wrote:
>>>
>>> I worked up a small patch to support Terabyte setting for memory.
>>> Which is OK, but it only works for 1TB, not for 2TB or above.
>>
>>
>> I've incorporated my review into a new version, attached.
>>
>> Added "TB" to the docs, added the macro KB_PER_TB, and made "show" to print
>> "1TB" rather than "1024GB".
>
> Looks good to me. But I found you forgot to change postgresql.conf.sample,
> so I changed it and attached the updated version of the patch.
>
> Barring any objection to this patch and if no one picks up this, I
> will commit this.

In truth, I hadn't realised somebody had added this to the CF. It was
meant to be an exploration and demonstration that further work was/is
required rather than a production quality submission. AFAICS it is
still limited to '1 TB' only...

Thank you both for adding to this patch. Since you've done that, it
seems churlish of me to interrupt that commit.

I will make a note to extend the support to higher values of TBs later.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-06-18 17:45:14 Re: SET work_mem = '1TB';
Previous Message D'Arcy J.M. Cain 2013-06-18 17:38:00 Re: A minor correction in comment in heaptuple.c