Re: Stored Procedure Performance

From: Adam Brusselback <adambrusselback(at)gmail(dot)com>
To: Purav Chovatia <puravc(at)gmail(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(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 16:54:37
Message-ID: CAMjNa7fwCbh4YuwUY5D7W5bM90aqUEqw-goYAvAt3UFvT0kjqg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> 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?

That is likely it. Comment that out and test.
If you still need to handle a unique violation, see if you can instead
use the ON CONFLICT clause on the INSERT.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Pavel Stehule 2017-10-11 19:06:42 Re: Stored Procedure Performance
Previous Message Purav Chovatia 2017-10-11 16:52:23 Re: Stored Procedure Performance