pgsql: Expand warnings on locks acquired by CREATE INDEX CONCURRENTLY

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Expand warnings on locks acquired by CREATE INDEX CONCURRENTLY
Date: 2011-06-13 21:25:21
Message-ID: E1QWEdN-0002sF-7G@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Expand warnings on locks acquired by CREATE INDEX CONCURRENTLY

The previous wording wasn't explicit enough, which could misled readers
into thinking that the locks acquired are more restricted in nature than
they really are. The resulting optimism can be damaging to morale when
confronted with reality, as has been observed in the field.

Greg Smith

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/9adda3e125642f41f256d1ed6adfe810b508e046

Modified Files
--------------
doc/src/sgml/ref/create_index.sgml | 11 ++++++++++-
1 files changed, 10 insertions(+), 1 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2011-06-13 21:59:16 pgsql: Fix aboriginal copy-paste mistake in error message
Previous Message Robert Haas 2011-06-13 17:04:42 pgsql: Remove parentheses from mention of current_schemas function.