Re: Table modifications with dependent views - best

Поиск
Список
Период
Сортировка
От David Roussel
Тема Re: Table modifications with dependent views - best
Дата
Msg-id 1114166069.20896.232479840@webmail.messagingengine.com
обсуждение исходный текст
Ответ на Re: Table modifications with dependent views - best practices?  (Michael Fuhr <mike@fuhr.org>)
Ответы Re: Table modifications with dependent views - best practices?  (Michael Fuhr <mike@fuhr.org>)
Re: Table modifications with dependent views - best  (Bruno Wolff III <bruno@wolff.to>)
Список pgsql-general
> I usually put DDL statements in a transaction, for a couple of
> reasons: so that a mistake doesn't leave me with half-done work
> (any error will cause the entire transaction to roll back), and to
> make the changes atomic for the benefit of other transactions.

Can you do that in postgres?  Will it really make the DDL atomic?

I know that is oracle any DDL will implicityly commit any existing
transaction, start another one, and commit again at the end of the
statement.

I think it is similar in SQL Server too.

Can postgress really do DDL on multiple tables and indexes atomically?

В списке pgsql-general по дате отправления:

Предыдущее
От: "Dinesh Pandey"
Дата:
Сообщение: Re: ShmemAlloc: out of memory
Следующее
От: "Dinesh Pandey"
Дата:
Сообщение: Table Partition