You can use the workload management feature that we've contributed to
Bizgres. That allows you to control the level of statement concurrency by
establishing queues and associating them with roles.
That would provide the control you are seeking.
- Luke
On 5/8/07 4:24 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> On Tue, 8 May 2007, Carlos Moreno wrote:
>
>> Daniel Griscom wrote:
>>>
>>> Several people have mentioned having multiple processors; my current
>>> machine is a uni-processor machine, but I believe we could spec the actual
>>> runtime machine to have multiple processors/cores.
>>
>> My estimate is that yes, you should definitely consider that.
>>
>>> I'm only running one query at a time; would that query be guaranteed to
>>> confine itself to a single processor/core?
>>
>> From what Joshua mentions, looks like you do have that guarantee.
>
> isn't there a way to limit how many processes postgres will create?
>
> if this is limited to 1, what happens when a vaccum run hits (or
> autovaccum)
>
> David Lang
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
