| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(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 19:48:24 |
| Message-ID: | 4D5ECD08.5020706@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-02-18 19:50:12 | Re: SR standby hangs |
| Previous Message | Robert Haas | 2011-02-18 19:44:34 | Re: WIP - Add ability to constrain backend temporary file space |