Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 3A9E0BEAE5C for ; Wed, 25 Jul 2012 14:01:44 -0300 (ADT) Received: from moutng.kundenserver.de ([212.227.17.10]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Su4xw-0005bW-ID for pgsql-performance@postgresql.org; Wed, 25 Jul 2012 17:01:43 +0000 Received: from alap2.localnet (p5DDC684A.dip.t-dialin.net [93.220.104.74]) by mrelayeu.kundenserver.de (node=mreu4) with ESMTP (Nemesis) id 0MKxYi-1Su4xb1Lua-0001lW; Wed, 25 Jul 2012 19:01:20 +0200 From: Andres Freund Organization: 2ndQuadrant.com To: pgsql-performance@postgresql.org Subject: Re: transactions start time Date: Wed, 25 Jul 2012 19:01:17 +0200 User-Agent: KMail/1.13.7 (Linux/3.5.0-rc3-andres-00231-g002b758; KDE/4.8.4; x86_64; ; ) Cc: Tom Lane , Aleksei Arefjev , Richard Huxton References: <22919.1343228180@sss.pgh.pa.us> In-Reply-To: <22919.1343228180@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201207251901.18070.andres@2ndquadrant.com> X-Provags-ID: V02:K0:jfag7yXjEzPXGN8sjKC1nAxflGvxcrAZsg8SCNU16E4 3h/Nz2lru4Vx/xwOjEvrfgQEucKnXWhLKzpppAfOZLrN23tVbQ 8VFWqzrECt6SVDRwoQmzY+eG6J81lTYxVC3zWnS83MjB2+MCmM 7KCuXBwOu2vjLOygKjCkQU3wh8HbRScJRLPTgEwfGc0tIMz2Tc 2/BJ+edZYpWpNGoXqB6JL57Q3mR3vsYbVkOf76NQiO1LVJmCrx ptPMWoCN4FXF7wy0FLDpmTvJBgXoqem1hMhkUFlWZY4pLIcbH3 Q1xmYqkTnQzP1jcXX4t0ssgyNqb+XJpRPhBctrpNoMsb37pOSR ihhMWDOnkMAhfc5826R0raa0ZI3fmVlt/NwaGJWkI X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201207/330 X-Sequence-Number: 47511 Hi, On Wednesday, July 25, 2012 04:56:20 PM Tom Lane wrote: > Aleksei Arefjev writes: > > On 24 July 2012 20:21, Richard Huxton wrote: > >> I'm not sure if I'm reading this right, but are there more than 48 > >> million BEGINs that took 0s each (presumably rounded down) and then a > >> handful taking about 0.8s? > > I'm wondering exactly where/how the duration was measured. If it was at > a client, maybe the apparent delay had something to do with network > glitches? It seems suspicious that all the outliers are around 0.8s. > It would be useful to look to see if there's any comparable pattern > for statements other than BEGIN. > > As Richard says, a BEGIN by itself ought to take negligible time. He earlier also asked on the IRC-Channel and I got the idea that the problem could be explained by pgbouncer in transaction pooling mode waiting for a free backend connection. Aleksei confirmed that they use pgbouncer in that configuration, so that might be it. Andres -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services