Re: Intermittent regression test failures from index-only plan changes

From: Simon Riggs <simon(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: Intermittent regression test failures from index-only plan changes
Date: 2012-01-08 15:53:02
Message-ID: CA+U5nMK073cZSQa6MDLh4BguWg7hao9AjQD-2zOJ3q0D4KQ7QQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jan 7, 2012 at 5:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> BTW, if you think this is a fatal issue, then I'm afraid it's also
> a fatal objection to your proposal to turn SnapshotNow into an MVCC
> snapshot.

Not just because of this, but I think its the wrong time in the cycle
to be completely rethinking catalog access semantics. Or put another
way, I'm too late and its too risky because the patch was becoming
enormous.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-01-08 16:19:48 Re: Should I implement DROP INDEX CONCURRENTLY?
Previous Message Kohei KaiGai 2012-01-08 15:52:04 [v9.2] LEAKPROOF attribute of FUNCTION (Re: [v9.2] Fix Leaky View Problem)