Re: WIP - Add ability to constrain backend temporary file space
| От | Josh Berkus |
|---|---|
| Тема | Re: WIP - Add ability to constrain backend temporary file space |
| Дата | |
| Msg-id | 4D5ECD08.5020706@agliodbs.com обсуждение исходный текст |
| Ответ на | Re: WIP - Add ability to constrain backend temporary file space (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: WIP - Add ability to constrain backend temporary file space
Re: WIP - Add ability to constrain backend temporary file space |
| Список | pgsql-hackers |
On 2/18/11 11:44 AM, Robert Haas wrote:
> On Fri, Feb 18, 2011 at 2:41 PM, Josh Berkus <josh@agliodbs.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
В списке pgsql-hackers по дате отправления: