| From: | Arthur Nascimento <tureba(at)gmail(dot)com> |
|---|---|
| To: | Arthur Filipe Martins Nascimento <tureba(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16867: savepoints vs. commit and chain |
| Date: | 2021-02-15 21:47:29 |
| Message-ID: | CALVFHFaBUXnCxv2kfG67=3NR=WPkVGgE_5Cf9S-LDPNYAwUORQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, 15 Feb 2021 at 17:54, PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> On a trivial transaction, I might do:
>
> =# begin;
> *=# commit and chain;
> *=# -- In this point I'm inside a second transaction
I forgot to mention that this case also works as expected:
=# begin;
*=# savepoint foo;
*=# release foo;
*=# commit and chain;
*=# -- In this point I'm also inside a second transaction
So it's only the unmatched savepoint/release transactions that are an issue.
I also attached the change I did to psql locally. But since it didn't
solve the issue, it's mostly for curiosity's sake.
Thanks,
Tureba - Arthur Nascimento
| Attachment | Content-Type | Size |
|---|---|---|
| psql-savepoint-cac.txt | text/plain | 924 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-02-15 23:26:48 | Re: BUG #16865: Regression: GIN Negated prefix search returns results that contain the search term |
| Previous Message | PG Bug reporting form | 2021-02-15 20:53:41 | BUG #16867: savepoints vs. commit and chain |