| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Press Release Draft - 2016-02-09 Cumulative Update |
| Date: | 2017-02-10 17:11:38 |
| Message-ID: | CA+TgmoZqZAEy_-_P_Gmj8PerYj+o8g3iwmSU4508f_R=2a7Y_g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 8, 2017 at 5:31 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Nullmeier | 2017-02-10 17:18:13 | Re: WIP: Faster Expression Processing and Tuple Deforming (including JIT) |
| Previous Message | Robert Haas | 2017-02-10 17:07:15 | Re: WIP: About CMake v2 |