Re: [COMMITTERS] pgsql: Release note updates.

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Release note updates.
Date: 2017-02-07 11:53:57
Message-ID: 20170207115357.ojk6wlewdcu36afa@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:
> Release note updates.
>
> Add item for last-minute CREATE INDEX CONCURRENTLY fix.

Hi,

Sorry for not noticing earlier, but there is a bug in the notes:

+ If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
+ that depends on a column not previously indexed, then rows inserted
+ or updated by transactions that ran concurrently with
+ the <command>CREATE INDEX</> command could have received incorrect
+ index entries.

CIC bug does not affect inserted rows, only updated rows, since the
bogus bitmap is only used to compute whether to omit index tuples for
HOT considerations.

Also, the bollixed rows do not receive incorrect index entries -- they
just do not receive any index entry at all.

May I suggest

+ If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
+ that depends on a column not previously indexed, then rows
+ updated by transactions that ran concurrently with
+ the <command>CREATE INDEX</> command could have missed receiving
+ index entries.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Pavan Deolasee 2017-02-07 12:03:56 Re: [COMMITTERS] pgsql: Release note updates.
Previous Message Tom Lane 2017-02-06 21:52:56 pgsql: Stamp 9.2.20.

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2017-02-07 12:03:56 Re: [COMMITTERS] pgsql: Release note updates.
Previous Message Mithun Cy 2017-02-07 11:44:19 Re: Proposal : For Auto-Prewarm.