Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e2K0H-0006XD-Ih for pgsql-performance@arkaria.postgresql.org; Wed, 11 Oct 2017 16:37:05 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e2K0H-0005SK-5c for pgsql-performance@arkaria.postgresql.org; Wed, 11 Oct 2017 16:37:05 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e2K0G-0005SB-Nk for pgsql-performance@postgresql.org; Wed, 11 Oct 2017 16:37:04 +0000 Received: from mail-oi0-x230.google.com ([2607:f8b0:4003:c06::230]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1e2K0E-0002Dy-B4 for pgsql-performance@postgresql.org; Wed, 11 Oct 2017 16:37:03 +0000 Received: by mail-oi0-x230.google.com with SMTP id j126so4016065oia.10 for ; Wed, 11 Oct 2017 09:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2MsUfAH3I3rCuOJ4QYv0VspqmMx0Ppdhfw2E2QdSl70=; b=jjgsGvfpCKbIb4JuzounFJkIRYwRC/3zPAC+F/m7QOKtIm4+0YQkDcxcxNO2N4S+29 6+MThBIBe5OUcnT7A8oALCIHBvnra3faElgcptQPZTRlqX3vwrt7yt7qVKQ43rvATjLo mTg68d97VtbunhU7SCWRTjIo5aPW5X6W/KO3k3L0wcXvCYjQANPJcW4kNiJgzoIq0H7e GxWcEzkWiDYJJshwA4polBOBmDu57mUtERI2412Iwd+rGU7zoHFq23CNWDZiY7Esukd1 UuopdySHh4WGXHMKmg3gWW2u5NXh7rarK/1JSE0Qds4tP3sYnGMZwQN6RyXFii/Ff/iL yCaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2MsUfAH3I3rCuOJ4QYv0VspqmMx0Ppdhfw2E2QdSl70=; b=MYDAlDE2XN6TBrJPJPmeNR3fwgH3ZnJesFlHEaktxdi6XzoSscCzVwZQMXStLK+XOK LlHJkL8qGJ9D/SvKit2UhJRXFtHt2NENOQB1K4guYDO/YAl6RT6RY2/X+2ZFoPipV2qQ /XdnNUowti/ZyInMC3z+nTVy3L68x7DbXfaYKsKkSIiym9B2sVIH2LUyXKnNHvB6gVk2 F1NSeenjy0vyhuoOFeE7sWwuBuqtDrQgar41xwm2FPvX+AZjA9bsaxu01RrIifefRtwL kUAS+/NkkDkkF38PRuNk+MqLXjPzJ7GU7OpWxWMHDOQHTU6bHPmoHV19pA7wGuKn8d0R GhAg== X-Gm-Message-State: AMCzsaWXKZWiOfbalUb1IAWlLHkNDAxV1rFePEcDJO08WddqESu/PvH+ QsDQO0rw9/fWZnxX/FWCaqzhiQmeORqi6SSEFH4= X-Google-Smtp-Source: AOwi7QCoAmpFo/Ku//tS/46CPAxR3qtZyA0D3YGUNlGuaBAo9cMDjVT359ITpaAfQDdPZTjekouEEflZPO+rFDpa1pM= X-Received: by 10.202.114.203 with SMTP id p194mr102472oic.327.1507739821637; Wed, 11 Oct 2017 09:37:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.6.162 with HTTP; Wed, 11 Oct 2017 09:37:01 -0700 (PDT) In-Reply-To: References: <1507042486.2998.1.camel@cybertec.at> From: Adam Brusselback Date: Wed, 11 Oct 2017 12:37:01 -0400 Message-ID: Subject: Re: Stored Procedure Performance To: Purav Chovatia Cc: Pavel Stehule , Laurenz Albe , "pgsql-performance@postgresql.org" Content-Type: text/plain; charset="UTF-8" List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Is there any error handling in there? I remember seeing performance issues if you put in any code to catch exceptions. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance