| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | David Klika <david(dot)klika(at)atlas(dot)cz> |
| Cc: | Sergei Kornilov <sk(at)zsrv(dot)org>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: 11 beta 3 / ROLLBACK TO SAVEPOINT regression in PLPGSQL |
| Date: | 2018-08-23 14:57:48 |
| Message-ID: | CAFj8pRAPu8AhN4PoqBGDtUgb++pMqmmi0cZm7Z_nYk6cSmncTg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
2018-08-23 16:45 GMT+02:00 David Klika <david(dot)klika(at)atlas(dot)cz>:
>
> > This routine works well on postgres v10:
> it works? Or is only accepted as input? I got error on function call.
> I thought plpgsql cannot directly uses savepoints, only implicitly with
> begin ... exception ... end block ( https://www.postgresql.org/
> docs/current/static/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING
> )
>
> Well, you can still create this function with set check_function_bodies to
> off
>
>
>
> This doesn't help, because any function is validated before execution
>
>
>
> but it is hard to believe, so it was working ever.
>
>
>
>
>
> You are right, calling the method lead to error in both cases. My
> misunderstanding, sorry. David
>
No problem :)
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-08-23 15:24:55 | Re: BUG #15342: pg_dump - XML with mixed content types generates invalid backup file |
| Previous Message | David Klika | 2018-08-23 14:45:02 | RE: 11 beta 3 / ROLLBACK TO SAVEPOINT regression in PLPGSQL |