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 CAB7nPqRjuDRi2Br1zuY3F7iN9+yAvGustLEyJLy3ZbuQ7KcoKQ@mail.gmail.com
Whole thread Raw
In response to Re: ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Thu, Jul 23, 2015 at 9:06 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Yeah, I think we should be able to define a collation in this case.
> For example it is as well possible to pass a WITH clause with storage
> parameters, though we do not document it in
> table_constraint_using_index
> (http://www.postgresql.org/docs/devel/static/sql-altertable.html).

Mistake here, please ignore this remark. USING INDEX does not accept
WITH storage_parameter but ADD CONSTRAINT without an index does and it
is documented in CREATE TABLE.
-- 
Michael



pgsql-hackers by date:

Previous
From: Kouhei Kaigai
Date:
Subject: Re: Parallel Seq Scan
Next
From: Paul Ramsey
Date:
Subject: Re: [PATCH] postgres_fdw extension support