Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e2MNj-0005QR-VQ for pgsql-performance@arkaria.postgresql.org; Wed, 11 Oct 2017 19:09:28 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e2MNi-0006C6-Vo for pgsql-performance@arkaria.postgresql.org; Wed, 11 Oct 2017 19:09:27 +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 1e2MLo-0002sB-4Q for pgsql-performance@postgresql.org; Wed, 11 Oct 2017 19:07:28 +0000 Received: from mail-wm0-x232.google.com ([2a00:1450:400c:c09::232]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1e2MLl-0005LK-CB for pgsql-performance@postgresql.org; Wed, 11 Oct 2017 19:07:26 +0000 Received: by mail-wm0-x232.google.com with SMTP id k4so7554178wmc.1 for ; Wed, 11 Oct 2017 12:07:24 -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=WX9Ld6KoEFAZZchZ4qrPq9m/sNMED/QKZGfJ7wdtAes=; b=VobCVJFiGHoYi4Xhf7jeqT4qjFJ5d3x11kM1LAe66QuInQqop4IXsY57vqMa3sH/f3 0gYwf90uMq5sw2vY4vg7tI7OJLSAdFT5mEZ8B2ib4W8UAzU2xMk70tlUxCHxAlmkSI9J 5zdX1WRuayOFzFzzL+AXlgE2f3wvKqqfpsVPmwFUs0Kcg868LBFGjsBw56uYYNfp1wJU 4KOid21O2ISWtOLGVeyR5zheKysU+jTQKFh7fOicfIDwkoQYUJ0OKfnOfK3hTYb41r1+ 0e0S98hR3bqZ+2syfDZs5EEe55WPF0SsKydH5Ncbgso2Ra6k3C0OSSXFs/eRw2mfdrwU eXMQ== 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=WX9Ld6KoEFAZZchZ4qrPq9m/sNMED/QKZGfJ7wdtAes=; b=D7hQ7h4GaECOe3fRLnS4u2sBzl+C2Wv4qZpS+QubA7PNr8Ir8xdGqwKOO1n4EFS8ig plDFQ5qorjeFkos9xJKESiE+5VvBHW4dRgsZM/qcS12QiyQC/A/HyFFoOGaNWtro8yzL YZsPXf0i/928J08R3LsNKMBojnPQx2dIVbpzrT+YoM/cF/XUW3bu6gbSgCXZ72Szlgvf sYsFXn4+Bdgua1ZQ0fL5GyNCLl9eitIMTfJrB1ioTcs6RoaZ3B5bQ5DlCAmhSjzRg4Tl egbCXK8yJoXOmMk7S+w3deZmYBb+M4/qxK16SVQ5PqnxZso5T637PYnq0TOmCRCzuW50 BR0Q== X-Gm-Message-State: AMCzsaW+JKvKungu/UKE0lF+aQD1KFdQNFbr5vIvM/lfrcDNBOapiMIu nOBB0j7ysZKCBAG1+szt5BYeaWVuw+flgTx6KgE= X-Google-Smtp-Source: AOwi7QDu+WHtVzNx7HxExKNxJAbDhzMScw/PLLMFNvqdnXxMyK76zVlMsdcnW7AM6s7mseU0PpjJi47wRXavv2qVvuE= X-Received: by 10.223.128.164 with SMTP id 33mr22123wrl.138.1507748843321; Wed, 11 Oct 2017 12:07:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.146.7 with HTTP; Wed, 11 Oct 2017 12:06:42 -0700 (PDT) In-Reply-To: References: <1507042486.2998.1.camel@cybertec.at> From: Pavel Stehule Date: Wed, 11 Oct 2017 21:06:42 +0200 Message-ID: Subject: Re: Stored Procedure Performance To: Purav Chovatia Cc: Adam Brusselback , Laurenz Albe , "pgsql-performance@postgresql.org" Content-Type: multipart/alternative; boundary="94eb2c069454377cfb055b4a22b8" 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 --94eb2c069454377cfb055b4a22b8 Content-Type: text/plain; charset="UTF-8" 2017-10-11 18:52 GMT+02:00 Purav Chovatia : > Yes, there is some code to catch exceptions like unique constraint > violation and no data found. Do you suggest we trying by commenting that > part? btw, the dataset is a controlled one, so what I can confirm is we are > not hitting any exceptions. > If it is possible, don't do it in cycle, or use exception handling only when it is necessary, not from pleasure. Regards Pavel > Thanks > > On 11 October 2017 at 22:07, Adam Brusselback > wrote: > >> Is there any error handling in there? I remember seeing performance >> issues if you put in any code to catch exceptions. >> > > --94eb2c069454377cfb055b4a22b8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


2017-10-11 18:52 GMT+02:00 Purav Chovatia <puravc@gmail.com>:
Yes, there is some = code to catch exceptions like unique constraint violation and no data found= . Do you suggest we trying by commenting that part? btw, the dataset is a c= ontrolled one, so what I can confirm is we are not hitting any exceptions.<= /div>

If it is possible, don't do it in= cycle, or use exception handling only when it is necessary, not from pleas= ure.

Regards

Pavel
<= div>

Thanks

On 11 October 2017 at 22:07= , Adam Brusselback <adambrusselback@gmail.com> wrote= :
Is there any error handling in there?= =C2=A0 I remember seeing performance
issues if you put in any code to catch exceptions.


--94eb2c069454377cfb055b4a22b8--