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 | 3993442.1668010649@sss.pgh.pa.us обсуждение |
| Ответ на | Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands (Yugo NAGATA <nagata@sraoss.co.jp>) |
| Ответы |
Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
|
| Список | pgsql-hackers |
Yugo NAGATA <nagata@sraoss.co.jp> writes:
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> What do you think of the attached wording?
> It looks good to me. That describes the expected behaviour exactly.
Pushed that, then.
>> I don't think the pipeline angle is of concern to anyone who might be
>> reading these comments with the aim of understanding what guarantees
>> they have. Perhaps there should be more about that in the user-facing
>> docs, though.
> I agree with that we don't need to mention pipelining in these comments,
> and that we need more in the documentation. I attached a doc patch to add
> a mention of commands that do internal commit to the pipelining section.
> Also, this adds a reference for the pipelining protocol to the libpq doc.
Hmm ... I don't really find either of these changes to be improvements.
The fact that, say, multi-table ANALYZE uses multiple transactions
seems to me to be a property of that statement, not of the protocol.
regards, tom lane
В списке pgsql-hackers по дате отправления: