Re: autocommit vs TRUNCATE et al
| От | Tom Lane |
|---|---|
| Тема | Re: autocommit vs TRUNCATE et al |
| Дата | |
| Msg-id | 13934.1034990666@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: autocommit vs TRUNCATE et al (Bruce Momjian <pgman@candle.pha.pa.us>) |
| Ответы |
Re: autocommit vs TRUNCATE et al
|
| Список | pgsql-hackers |
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> ... I think we
> should just do an automatic COMMIT if it is the first statement of a
> transaction, and if not, throw the same error we used to throw. We are
> performing autocommit for SET at the start of a transaction now anyway,
> so it isn't totally strange to do it for TRUNCATE, etc. too. In fact,
> you can just put the xact commit check in the same place SET is handled
> in postgres.c. It isn't great, but it is clean. ;-)
Well, "clean" isn't the adjective I would use ;-), but this might be the
most useful approach. The analogy to SET hadn't occurred to me.
regards, tom lane
В списке pgsql-hackers по дате отправления: