Re: SET work_mem = '1TB';

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SET work_mem = '1TB';
Date: 2013-06-18 17:59:45
Message-ID: CA+U5nMLfkj+ssSccbS=hXKp+m_D_Y1bTUkjH8iR+U_vrffqDGA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18 June 2013 18:45, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> 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...
>
> At the beginning of the CF, I do a sweep of patch files emailed to
> -hackers and not in the CF. I believe there were three such of yours,
> take a look at the CF list. Like I said, better to track them
> unnecessarily than to lose them.

Thanks. Please delete the patch marked "Batch API for After Triggers".
All others are submissions by me.

--
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 Kevin Grittner 2013-06-18 18:04:25 Re: A minor correction in comment in heaptuple.c
Previous Message Josh Berkus 2013-06-18 17:54:54 Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])