| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Giuseppe Sacco <giuseppe(at)eppesuigoccas(dot)homedns(dot)org> |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: Over commit? |
| Date: | 2009-03-11 08:55:04 |
| Message-ID: | 937d27e10903110155g3bce3992y73aeb39cf82d32ab@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Wed, Mar 11, 2009 at 7:55 AM, Giuseppe Sacco
<giuseppe(at)eppesuigoccas(dot)homedns(dot)org> wrote:
> Hi hackers,
>
> #: pgadmin/schema/gpResQueue.cpp:122
> msgid "Over commit?"
> msgstr ""
>
> Could you please explain what this sentence means?
It's a Greenplum thing, relating to resource queues which allow you to
manage workload in the system. From the docs:
Cost Threshold Overcommit
If a resource queue is limited based on a cost threshold, then the
administrator can
allow OVERCOMMIT (the default). Resource queues with a cost threshold and
overcommit enabled will allow a query that exceeds the cost threshold to run,
provided that there are no other queries in the queue at the time the
query is submitted.
The cost threshold will only be enforced if there are multiple
sessions submitting
queries through the queue at once.
If NOOVERCOMMIT is specified, then queries that exceed the cost limit
will always be
rejected and never allowed to run.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashesh Vashi | 2009-03-11 09:11:36 | Patch: Crash on linux-x64 |
| Previous Message | svn | 2009-03-11 08:44:44 | SVN Commit by dpage: r7671 - trunk/pgadmin3/pgadmin/schema |