Re: ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard
Дата
Msg-id CAB7nPqTF6zpLvrBWDgi4hvSH_7f519OAepTsqF5r4rTcs-tcQg@mail.gmail.com
обсуждение исходный текст
Ответ на ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard  (Michael Paquier <michael.paquier@gmail.com>)
Re: ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Wed, Jul 22, 2015 at 1:23 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> Notice that the collation specifier is gone.  Oops.

As it is not possible to specify directly a constraint for a PRIMARY
KEY expression, what about switching dumpConstraint to have it use
first a CREATE INDEX query with the collation and then use ALTER TABLE
to attach the constraint to it? I am noticing that we already fetch
the index definition in indxinfo via pg_get_indexdef. Thoughts?
-- 
Michael



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

Предыдущее
От: Qingqing Zhou
Дата:
Сообщение: Planner debug views
Следующее
От: Andreas Karlsson
Дата:
Сообщение: Re: [PATCH] Reload SSL certificates on SIGHUP