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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Gurjeet Singh <gurjeet(at)singh(dot)im>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER TABLE .. ADD PRIMARY KEY .. USING INDEX has dump-restore hazard
Date: 2015-07-23 14:19:42
Message-ID: CAB7nPqRjuDRi2Br1zuY3F7iN9+yAvGustLEyJLy3ZbuQ7KcoKQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 23, 2015 at 9:06 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul Ramsey 2015-07-23 14:48:49 Re: [PATCH] postgres_fdw extension support
Previous Message Kouhei Kaigai 2015-07-23 14:13:45 Re: Parallel Seq Scan