| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Purav Chovatia <puravc(at)gmail(dot)com> |
| Cc: | Adam Brusselback <adambrusselback(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Stored Procedure Performance |
| Date: | 2017-10-11 19:06:42 |
| Message-ID: | CAFj8pRBiBN9T9bCMfyT2oQ7SAP1Aq9wH5=b=yBkA1W6O-HGTvQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
2017-10-11 18:52 GMT+02:00 Purav Chovatia <puravc(at)gmail(dot)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 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 <adambrusselback(at)gmail(dot)com>
> wrote:
>
>> Is there any error handling in there? I remember seeing performance
>> issues if you put in any code to catch exceptions.
>>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2017-10-11 21:08:55 | Re: blocking index creation |
| Previous Message | Adam Brusselback | 2017-10-11 16:54:37 | Re: Stored Procedure Performance |