Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42770=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1XKvB5-0003Bf-Su
 for pgsql-admin@arkaria.postgresql.org; Fri, 22 Aug 2014 20:11:16 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42770=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1XKvB5-0007eR-7d
 for pgsql-admin@arkaria.postgresql.org; Fri, 22 Aug 2014 20:11:15 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <jayknowsunix@gmail.com>)
 id 1XKvB4-0007eL-FH
 for pgsql-admin@postgresql.org; Fri, 22 Aug 2014 20:11:14 +0000
Received: from mail-qg0-x22f.google.com ([2607:f8b0:400d:c04::22f])
 by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.80) (envelope-from <jayknowsunix@gmail.com>)
 id 1XKvB0-0000V5-Ew
 for pgsql-admin@postgresql.org; Fri, 22 Aug 2014 20:11:13 +0000
Received: by mail-qg0-f47.google.com with SMTP id i50so10552530qgf.20
 for <pgsql-admin@postgresql.org>; Fri, 22 Aug 2014 13:11:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=references:mime-version:in-reply-to:content-type
 :content-transfer-encoding:message-id:cc:from:subject:date:to;
 bh=LZrJemAHyHSa1HyeuIt6FwA9PNfKYs8S6sr/XKgQ8wI=;
 b=mOFG1qWJjLz5jLqfM/G0pv2i10jt5Ewx/OJJJCdUVgVrcexdymUdb7L3ak+AxB3Zsw
 l9oZyekquy7tdUWUlqG1WzHHxdlFkXaeOBIc5J1RhPy8hXBNBA4XKwG7YkBeIxL3dYag
 W/9zMD0ZslyDjOQW6ajJfNHwCVSJQ2WMyiyef1MV5zRDy2wtbnRUqU24JoETrq8C3Mgz
 OWrA0FX74q30ipbRe0L/O3wVZ9h5XIPF6iqVgBqqKJQDCBqDqG8eFcQcKB2nE6Ev2+kR
 wQ6IND3cKUaa5lm2anLOWDus+WwcRrhBR0JQmY4bOqjzKZqRfrwXz2dFymkZ0v3vYps7
 zJSQ==
X-Received: by 10.224.75.130 with SMTP id y2mr11635071qaj.72.1408738267385;
 Fri, 22 Aug 2014 13:11:07 -0700 (PDT)
Received: from [192.168.254.1] (h77.89.102.166.static.ip.windstream.net.
 [166.102.89.77])
 by mx.google.com with ESMTPSA id x14sm37471202qae.13.2014.08.22.13.11.06
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Fri, 22 Aug 2014 13:11:06 -0700 (PDT)
References: 
 <CAFiWeJB30=ncjt3gHuYh61ke4x--HA_2xkA9vxxU6puLZTNmCw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: 
 <CAFiWeJB30=ncjt3gHuYh61ke4x--HA_2xkA9vxxU6puLZTNmCw@mail.gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <15C963C4-539B-4A88-9C21-54C3221FD1D7@gmail.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
X-Mailer: iPad Mail (11D257)
From: jayknowsunix@gmail.com
Subject: Re: Problems with PG 9.3
Date: Fri, 22 Aug 2014 16:11:06 -0400
To: Dhruv Shukla <dhruvshukla82@gmail.com>
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Have you tried attaching strace to one the loaders? That might give a clue =
where it's getting stuck.
-
Jay

Sent from my iPad

> On Aug 22, 2014, at 3:23 PM, Dhruv Shukla <dhruvshukla82@gmail.com> wrote:
>=20
> Hello,
> We quite recently moved our production database from 8.4 to 9.3. Its been=
 just 2 months and the features which it allows for parallel backup and rec=
overy has been a great use for us.
> But with 9.3 we have also run into a lot of troubles.
>=20
> Some background:
> We run loaders to load data into the DB. These loaders are perl programs =
which run on a different server than the db server. The amount of data load=
ed each day is pretty high.
>=20
> Problem:
> Some of the loaders are performing in a bad way. they get stuck or EOF ha=
ppens on client connection and things just dies. There is one piece which g=
ets stuck daily ... but once killed runs normal.
>=20
> One of the episode of today one of the loader got stuck for 2hr 15 min. I=
 killed the whole process, restarted it and things ran within 10 mins. What=
 I observed was the DB load hadnt changed or shifted significantly between =
the killing and the end of the program. At first we were thinking it was lo=
aders but now it looks as if its the postgres database.=20
>=20
> The piece where it was stuck for 2hrs was it was trying to insert 37K row=
s in a 500K row table, which is pretty small considering PG potential. But =
the bottleneck here we cant solve it.
>=20
>=20
> Kindly help me find the solution, or the right place to dig into to find =
the exact problem, its been troubling some of our loaders for quite some ti=
me now.=20
>=20
> Please let me know if you need further information regarding the settings=
 on our DB server.
>=20
> --=20
> Regards
> Dhruv


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin