Re: Tricky bugs in concurrent index build

Поиск
Список
Период
Сортировка
От Gregory Stark
Тема Re: Tricky bugs in concurrent index build
Дата
Msg-id 87ejv4u28p.fsf@enterprisedb.com
обсуждение исходный текст
Ответ на Re: Tricky bugs in concurrent index build  (Alvaro Herrera <alvherre@commandprompt.com>)
Ответы Re: Tricky bugs in concurrent index build  ("Jim C. Nasby" <jnasby@pervasive.com>)
Список pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:

> That was what the patch originally used, but it was changed because it
> made difficult for psql to auto-complete that.

Psql has to be able to parse it not for auto-completion but because it needs
to know that it's not a transactional command. The regular CREATE INDEX can be
run from within a transaction but online index builds use two transactions on
their own so psql has to know not to insert a BEGIN and savepoint around it.

I'll use this opportunity to plug that feature again. I think most people
should use autocommit off with on_error_rollack on for most of their daily
use. Being able to double check the results of my ad-hoc updates before
committing them saved me more headaches than I can count with Oracle.
Autocommit off only became practical for interactive use with postgres when
savepoints showed up.


--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


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

Предыдущее
От: "Zeugswetter Andreas DCP SD"
Дата:
Сообщение: Re: Tricky bugs in concurrent index build
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Tricky bugs in concurrent index build