Re: [HACKERS] Press Release Draft - 2016-02-09 Cumulative Update - Mailing list pgsql-hackers

From Jonathan S. Katz
Subject Re: [HACKERS] Press Release Draft - 2016-02-09 Cumulative Update
Date
Msg-id 1567DB2E-AA46-4268-AA71-AA004CA5A075@postgresql.org
Whole thread Raw
In response to Re: [HACKERS] Press Release Draft - 2016-02-09 Cumulative Update  (Michael Banck <michael.banck@credativ.de>)
List pgsql-hackers
> On Feb 7, 2017, at 4:39 PM, Michael Banck <michael.banck@credativ.de> wrote:
>
> Hi,
>
> Am Dienstag, den 07.02.2017, 15:58 -0500 schrieb Jonathan S. Katz:
>
>
>>
https://git.postgresql.org/gitweb/?p=press.git;a=blob;f=update_releases/current/20170209updaterelease.txt;h=f90d4716f240dbea4cca647b099f79865545b633;hb=d85498c284275bcab4752b91476834de780648b8
>
> It says "[...]then rows that were updated by transactions running at the
> same time as the CREATE INDEX CONCURRENTLY command could have been index
> incorrectly."
>
> That sounds off to me, shouldn't it be "indexed incorrectly" or
> something?

Yes, passive voice :(  I’ve made the modification on my local copy and will push it up after the resolution on the
CREATEINDEX recipe. 

Jonathan


pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: [HACKERS] Press Release Draft - 2016-02-09 Cumulative Update
Next
From: Tom Lane
Date:
Subject: [HACKERS] Caching index AM working data across aminsert calls