| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP - Add ability to constrain backend temporary file space |
| Date: | 2011-02-18 20:37:34 |
| Message-ID: | AANLkTi==xu-LRoHHMuPHAHfLU2r3W1ziKKPoycH+UY9s@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 18, 2011 at 2:48 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 2/18/11 11:44 AM, Robert Haas wrote:
>> On Fri, Feb 18, 2011 at 2:41 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>>> Second, the main issue with these sorts of macro-counters has generally
>>> been their locking effect on concurrent activity. Have you been able to
>>> run any tests which try to run lots of small externally-sorted queries
>>> at once on a multi-core machine, and checked the effect on throughput?
>>
>> Since it's apparently a per-backend limit, that doesn't seem relevant.
>
> Oh! I missed that.
>
> What good would a per-backend limit do, though?
>
> And what happens with queries which exceed the limit? Error message? Wait?
Well I have not RTFP, but I assume it'd throw an error. Waiting isn't
going to accomplish anything.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-02-18 20:42:58 | Re: SR standby hangs |
| Previous Message | Heikki Linnakangas | 2011-02-18 20:30:08 | Re: review: FDW API |