Re: brin index vacuum versus transaction snapshots - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: brin index vacuum versus transaction snapshots
Date
Msg-id 20150730200140.GV2441@postgresql.org
Whole thread Raw
In response to brin index vacuum versus transaction snapshots  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: brin index vacuum versus transaction snapshots  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: brin index vacuum versus transaction snapshots  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-hackers
Kevin Grittner wrote:
> If you run `make installcheck` against a cluster with
> default_transaction_isolation = 'repeatable read' you get one
> failure:

I am tempted to say that we should just disallow to run vacuum on a
table containing a brin index in a transaction-snapshot transaction.
It is possible to silence the problem by checking for vacuum flags, but
(without testing) I think there will be a problem because the snapshot
is acquired too early and it is possible for concurrent transactions to
insert tuples in the table that the summarizing scan will not see, which
will cause the index to become effectively corrupt.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Remaining 'needs review' patchs in July commitfest
Next
From: Robert Haas
Date:
Subject: Re: Support for N synchronous standby servers - take 2