On Wed, Feb 8, 2017 at 5:31 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> 11 There existed a race condition /where/ if CREATE INDEX CONCURRENTLY was
> called on a column that had not been indexed before, then rows that were
> updated by transactions running at the same time as the CREATE INDEX
> CONCURRENTLY command /may not/ have been indexed incorrectly.
I think this is moot at this point, but "may not have been indexed
incorrectly" seems to have two negatives where there should be only
one.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company