Re: Catching errors inside a LOOP is causing performance issues

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Denisa Cirstescu <Denisa(dot)Cirstescu(at)tangoe(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Catching errors inside a LOOP is causing performance issues
Date: 2017-09-28 15:02:14
Message-ID: CAKFQuwabnERrrAPKJaTaJ_RBuDvfoDZbinnqed+DPPeHYkJnCw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 28, 2017 at 1:08 AM, Denisa Cirstescu <
Denisa(dot)Cirstescu(at)tangoe(dot)com> wrote:

> Hi Tom,
>
> You said that trapping an *arbitrary* exception is a “fairly expensive
> mechanism”.
>
​I suppose a better (though maybe not perfectly accurate) wording is that
setting up the pl/pgsql execution layer to trap "arbitrary SQL-layer
exceptions"​ is fairly expensive. Even if the user specifies specific
errors the error handling mechanism in pl/pgsql is code for generic
(arbitrary) errors being given to it.

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message kbrannen 2017-09-28 15:02:44 pg_stat_tmp and pg_upgrade
Previous Message Seamus Abshere 2017-09-28 14:34:59 Function to return per-column counts?