From: Tobias Brox <tobias@nordicbet.com>
To: Madison Kelly <linux@alteeve.com>
Cc: Tobias Brox <tobias@nordicbet.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Setting "nice" values
Date: Mon, 6 Nov 2006 14:33:53 +0100
Message-ID: <20061106133353.GA22050@oppetid.no> (raw)
In-Reply-To: <454F3434.4030205@alteeve.com>
References: <20061102160057.GA26580@oppetid.no>
<454F3434.4030205@alteeve.com>
[Madison Kelly - Mon at 08:10:12AM -0500]
> to run, which puts it into your "drawback" section. The server in
> question is also almost under load of some sort, too.
>
> A great tip and one I am sure to make use of later, thanks!
I must have been sleepy, listing up "cons" vs "drawbacks" ;-)
Anyway, the central question is not the size of the job, but the size of
the transactions within the job - if the job consists of many
transactions, "my" test can be run before every transaction. Having
transactions lasting for hours is a very bad thing to do, anyway.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tobias@nordicbet.com, linux@alteeve.com, smarlowe@g2switchworks.com
Subject: Re: Setting "nice" values
In-Reply-To: <20061106133353.GA22050@oppetid.no>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox