On Sun, May 10, 2015 at 11:28 AM, David G. Johnston <
david.g.johnston@gmail.com> wrote:
> Please don't top-post.
>
> On Sun, May 10, 2015 at 11:19 AM, <postgresql2@realityexists.net> wrote:
>
>> That's odd! I just confirmed again that I get the exact same error with
>> COMMIT (and no warnings). Are you able to run all the commands before th=
e
>> COMMIT successfully and get 1 row back from the SELECT?
>>
>>
> =E2=80=8BI am. I am not using psql so I may be getting different errors =
compared
> to what psql would eventually emit. I suspect that the actual error is
> getting swallowed somewhere and then the processing on the COMMIT happens
> without the transaction being open.
>
=E2=80=8BTo clarify - the transaction still errors out; but to me, not usin=
g psql,
it seems to do so prior =E2=80=8Bto the COMMIT itself being processed and s=
o the
commit emits a warning about not being in a tranasction.
Ubuntu apt.postgresql.org 9.3.5
David J.
