Re: {CREATE INDEX, REINDEX} CONCURRENTLY improvements

Alvaro Herrera <alvherre@alvh.no-ip.org>

From: Álvaro Herrera <alvherre@alvh.no-ip.org>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>, Hamid Akhtar <hamid.akhtar@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-02-23T00:15:31Z
Lists: pgsql-hackers

Attachments

On 2021-Feb-22, Álvaro Herrera wrote:

> Here's an updated patch.
> 
> I haven't added commentary or documentation to account for the new
> assumption, per Matthias' comment and Robert's discussion thereof.

Done that.  I also restructured the code a bit, since one line in
ComputedXidHorizons was duplicative.


-- 
Álvaro Herrera                            39°49'30"S 73°17'W
Tom: There seems to be something broken here.
Teodor: I'm in sackcloth and ashes...  Fixed.
        http://archives.postgresql.org/message-id/482D1632.8010507@sigaev.ru

Commits

  1. VACUUM: ignore indexing operations with CONCURRENTLY

  2. Avoid spurious wait in concurrent reindex

  3. Invent struct ReindexIndexInfo