Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
От | Tom Lane |
---|---|
Тема | Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands |
Дата | |
Msg-id | 2361330.1658851386@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
|
Список | pgsql-bugs |
"David G. Johnston" <david.g.johnston@gmail.com> writes: > That leaves us with changing the documentation then, from: > CREATE DATABASE cannot be executed inside a transaction block. > to: > CREATE DATABASE cannot be executed inside an explicit transaction block (it > will error in this case), and will commit (or rollback on failure) any > implicit transaction it is a part of. That's not going to help anybody unless we also provide a definition of "implicit transaction", which is a bit far afield for that man page. I did miss a bet in the proposed pipeline addendum, though. I should have written ... However, there are a few DDL commands (such as <command>CREATE DATABASE</command>) that cannot be executed inside a transaction block. If one of these is executed in a pipeline, it will, upon success, force an immediate commit to preserve database consistency. That ties the info to our standard wording in the per-command man pages. regards, tom lane
В списке pgsql-bugs по дате отправления: