Re: brin index vacuum versus transaction snapshots

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: brin index vacuum versus transaction snapshots
Date: 2015-07-21 23:32:07
Message-ID: CAMkU=1xXTejSWEti5ajr1hOvVLi4ttp0Ma4o8ueRtNWMQEdznA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 21, 2015 at 3:10 PM, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:

> Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
>
> > If you run `make installcheck` against a cluster with
> > default_transaction_isolation = 'repeatable read' you get one
> > failure:
>
> > + ERROR: brin_summarize_new_values() cannot run in a transaction that
> has already obtained a snapshot
>
> > This is using source at commit 9faa6ae14f6098e4b55f0131f7ec2694a381fb87.
>
> Ah, the very next commit fixed this while I was running the tests.
>
> Nothing to see here, folks; move along....
>

Still looks broken from here.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2015-07-22 00:02:44 Re: pgbench stats per script & other stuff
Previous Message Jolly Chen 2015-07-21 22:42:04 "A huge debt of gratitude" - Michael Stonebraker