Re: "A block containing an EXCEPTION clause is significantly more expensive to enter and exit than a block without one"

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Bryn Llewellyn <bryn(at)yugabyte(dot)com>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>, Tom Lane PostgreSQL <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Subject: Re: "A block containing an EXCEPTION clause is significantly more expensive to enter and exit than a block without one"
Date: 2022-06-13 20:07:45
Message-ID: D1837AA1-ADF0-4236-8BEC-08A1357A77AE@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Jun 12, 2022, at 23:07, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> The lazy implementation theoretically can be possible, but why?

Isn't one of the reasons for the savepoint (in fact, the principal reason) to reset the connection back to non-error state so that execution can continue? In that case, it really does need to create the savepoint at the start of the block, regardless of what's in it, since any statement can raise an error.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joel Rabinovitch 2022-06-13 21:52:00 Tools to convert timestamp data to another time zone in PostgreSQL
Previous Message Tom Lane 2022-06-13 19:38:54 Re: "A block containing an EXCEPTION clause is significantly more expensive to enter and exit than a block without one"