Re: Word-smithing doc changes

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>

To: Greg Smith <greg@2ndQuadrant.com>

Cc: Greg Stark <stark@mit.edu>, Alvaro Herrera <alvherre@commandprompt.com>, "<pgsql-hackers@postgresql.org>" <pgsql-hackers@postgresql.org>

Date: 2012-08-03T13:59:36Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Expand warnings on locks acquired by CREATE INDEX CONCURRENTLY
- a03feb9354bd 9.2.0 cited

Attachments

concurrent.diff (text/x-diff) patch

On Fri, Aug  3, 2012 at 12:26:56AM -0400, Bruce Momjian wrote:
> The concurrent index documentation under discussion above was never
> updated, so I took a stab at it, attached.
> 
> Greg, I looked at adding a mention of the virtual transaction wait to
> the "explicit-locking" section as you suggested, and found those were
> all user-visible locking, while this is internal locking.  I did find a
> clear description of transaction id locking in the pg_locks system view
> docs, so I just referenced that.

I found a way to clarify the wording further;  patch attached.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +