I'd like to propose the following slight rewording for the note about ALTER
TABLE ... ADD table_constraint_using_index. The existing text says one may
"install it [the existing index] as an official constraint".
The "official constraint" phrase sounds like weasel wording to me -- how is
a UNIQUE constraint more "official" than an UNIQUE index? Then "install"
makes it sound like some installation process is going on that you should
be aware of. I like "convert" slightly better instead.
Josh
diff --git a/doc/src/sgml/ref/alter_table.sgml
b/doc/src/sgml/ref/alter_table.sgml
new file mode 100644
index 92e9ce8..784f5b4
*** a/doc/src/sgml/ref/alter_table.sgml
--- b/doc/src/sgml/ref/alter_table.sgml
*************** ALTER TABLE ALL IN TABLESPACE <replaceab
*** 320,327 ****
Adding a constraint using an existing index can be helpful in
situations where a new constraint needs to be added without blocking
table updates for a long time. To do that, create the index using
! <command>CREATE INDEX CONCURRENTLY</>, and then install it as an
! official constraint using this syntax. See the example below.
</para>
</note>
</listitem>
--- 320,327 ----
Adding a constraint using an existing index can be helpful in
situations where a new constraint needs to be added without blocking
table updates for a long time. To do that, create the index using
! <command>CREATE UNIQUE INDEX CONCURRENTLY</>, and then convert it to a
! constraint using this syntax. See the example below.
</para>
</note>
</listitem>
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
