Received: from localhost (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 665D86331C2
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Thu,  5 Nov 2009 09:25:48 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024)
	with ESMTP id 12263-02-3
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Thu,  5 Nov 2009 13:25:25 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com
	[209.85.218.213])
	by mail.postgresql.org (Postfix) with ESMTP id 8C6D3635867
	for <pgsql-performance@postgresql.org>;
	Thu,  5 Nov 2009 09:25:23 -0400 (AST)
Received: by bwz5 with SMTP id 5so857608bwz.3
	for <pgsql-performance@postgresql.org>;
	Thu, 05 Nov 2009 05:25:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type;
	bh=UGM4KDZLmDPnBSn9cJ81WZdHPtPogc/jIxMM9wXqEoo=;
	b=YPHaFNgILikJZMJHntl036BbinI3EugLG61P4T3UISLrHEeHc0tWr3UTzo6itaDark
	lUOcY1P4Wm2nmM8sbhZAhey9XcuJk6mneYp256FPcbpyXRYMKznj+9uk6DbguTGh3Oxt
	ZzK8UU2iQu0p7lhx0i/q41xKaDZ9chAJJ6VP8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	b=xwbTBL5PF3/klMspK3BhjcWqTcNkzerw4mP+WsVf/oFuW5uQraJfyNHSrSjo2SrP8P
	P354SdtQOaa91v2ZBQVHRrjuax2OA5qWhvZH8meJznxLn1flxIrWgph7MeSggUCome5g
	a2027NRf7B1JFiXOaQuhXbVhB0tXlcy+6hGcE=
MIME-Version: 1.0
Received: by 10.204.153.24 with SMTP id i24mr1494087bkw.114.1257427520794;
	Thu, 05 Nov 2009 05:25:20 -0800 (PST)
In-Reply-To: <abf9211d0911050520t72a5d6dfv877ced07077b11@mail.gmail.com>
References: <abf9211d0911050136g48739f0ft53b63f96cddf706@mail.gmail.com>
	<2f4958ff0911050138n3f246b7ck6182cb702ac48e91@mail.gmail.com>
	<407d949e0911050332n5ef355c1y156dcd26aa28d222@mail.gmail.com>
	<abf9211d0911050520t72a5d6dfv877ced07077b11@mail.gmail.com>
Date: Thu, 5 Nov 2009 13:25:20 +0000
Message-ID: <2f4958ff0911050525w678925uc8f63fe966951ef5@mail.gmail.com>
Subject: Re: Running some query in low priority
From: =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= <gryzman@gmail.com>
To: S Arvind <arvindwill@gmail.com>
Cc: pgsql-performance@postgresql.org
Content-Type: multipart/alternative; boundary=0015175dd9ceb5317904779fa831
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.381 tagged_above=-10 required=5 tests=AWL=0.217,
	BAYES_00=-2.599, HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 200911/67
X-Sequence-Number: 36235

--0015175dd9ceb5317904779fa831
Content-Type: text/plain; charset=UTF-8

On Thu, Nov 5, 2009 at 1:20 PM, S Arvind <arvindwill@gmail.com> wrote:

> Thank Greg and Grzegorz,
>        As told i have large batch load to the postgres which i need to be
> run in low priority. Is it really throttling the data will help to lower the
> postgres workload for some queries?
>
depends on what you are actually trying to achieve.

If it is an insert of some sort, than divide it up. If it is a query that
runs over data, use limits, and do it in small batches. Overall, divide in
conquer approach works in these scenarios.



-- 
GJ

--0015175dd9ceb5317904779fa831
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Thu, Nov 5, 2009 at 1:20 PM, S Arvind=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:arvindwill@gmail.com">arvindwill@g=
mail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; p=
adding-left: 1ex;">
Thank Greg and Grzegorz,<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 As told i =
have  large batch load to the postgres which i need to be run in low priori=
ty. Is it really throttling the data will help to lower the postgres worklo=
ad for some queries?<br></blockquote>
<div>depends on what you are actually trying to achieve.<br><br>If it is an=
 insert of some sort, than divide it up. If it is a query that runs over da=
ta, use limits, and do it in small batches. Overall, divide in conquer appr=
oach works in these scenarios.<br>
<br></div></div><br clear=3D"all"><br>-- <br>GJ<br>

--0015175dd9ceb5317904779fa831--