| 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: | Bruce Momjian <bruce(at)momjian(dot)us>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands |
| Date: | 2022-07-26 16:14:19 |
| Message-ID: | 2363212.1658852059@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> And we are back around to the fact that only by using libpq directly, or
> via the pipeline feature of pgbench, can one actually exert control over
> the implicit transaction. The psql and general SQL interface
> implementation are just going to Sync after each command and so everything
> looks like one transaction per command to them and only explicit
> transactions matter.
Right.
> From that, the adjustment you describe above is sufficient for me.
Cool, I'll set about back-patching.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-07-27 02:15:20 | Re: could not link file in wal restore lines |
| Previous Message | David G. Johnston | 2022-07-26 16:11:52 | Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhang Mingli | 2022-07-26 16:16:33 | [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO |
| Previous Message | David G. Johnston | 2022-07-26 16:11:52 | Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands |