| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Srinivasa T N <seenutn(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Meaning of below statement |
| Date: | 2020-11-20 15:41:56 |
| Message-ID: | 1301063.1605886916@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Friday, November 20, 2020, Srinivasa T N <seenutn(at)gmail(dot)com> wrote:
>> 2020-11-20 11:20:46.218 IST [38207] LOG: execute S_3: ROLLBACK
> If there was an error you would see an error message. Plus, PostgreSQL
> doesn’t just internally issue a rollback on its own. That said I’m not
> sure what is being shown, or rather where the “execute” stuff comes from.
The "execute" says this is an execution of a previously prepared query,
ie the client is using extended query protocol rather than simple.
It's got nothing much to do with the semantics though. It seems clear
that the client chose to roll back the transaction; the server did not
do that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zwettler Markus (OIZ) | 2020-11-20 16:12:25 | AW: AW: Linux package upgrade without dependency conflicts |
| Previous Message | Magnus Hagander | 2020-11-20 15:28:31 | Re: Linux package upgrade without dependency conflicts |