Postgres Pro
Downloads
Home   >   mailing lists

Re: ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard
Date
Msg-id CAB7nPqTF6zpLvrBWDgi4hvSH_7f519OAepTsqF5r4rTcs-tcQg@mail.gmail.com
Whole thread Raw
In response to ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard
Re: ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard
List pgsql-hackers
Tree view 
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 by date:

Previous
From: Qingqing Zhou
Date:
Subject: Planner debug views
Next
From: Andreas Karlsson
Date:
Subject: Re: [PATCH] Reload SSL certificates on SIGHUP