| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Transaction issue |
| Date: | 2024-06-20 12:44:40 |
| Message-ID: | ZnQkOEd87b66GQft@hermes.hilbert.loc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am Wed, Jun 19, 2024 at 02:32:07PM -0700 schrieb Rich Shepard:
> Yes, I see how this works if the transaction is committed. But before I
> commit the transaction I run a select statement to ensure the rows added are
> correct. Can I rollback a commited transaction? I've assumed not, so I won't
> commit the transaction without testing. And I'm not getting a detailed error
> message.
Shot in the dark: are you be any chance using tab-completion
when running the SELECT before the COMMIT ?
I've seen it happen a few times that tab completion ran
queries behind the scenes which failed and thereby set the
open transaction to abort state ...
And, no, I can't reproduce :/
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2024-06-20 13:04:56 | Re: Transaction issue |
| Previous Message | Ron Johnson | 2024-06-20 12:25:19 | Re: Help. The database was created using collation version 2.17, but the operating system provides version 2.34. |