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-07 10:29:43
Message-ID: CA+U5nML9jEho+poM9y6S78WLWhd-24uvSCPVm95JpJZSVXX7Eg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 6, 2012 at 10:25 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Background auto-VACUUMs shouldn't cause this problem because they don't
> take snapshots, and ideally it'd be nice if auto-ANALYZE couldn't create
> the issue either, but ANALYZE does need a snapshot so it's hard to see
> how to avoid having it trip the all-visible logic.  Anybody have any
> ideas?

That seems like a huge production problem looming over us, not just a
regression test issue.

I feel like this is a trick question, but I'll ask anyway: Can't we
just ignore ANALYZE?

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-01-07 10:55:19 Re: 16-bit page checksums for 9.2
Previous Message Heikki Linnakangas 2012-01-07 10:26:42 Re: 16-bit page checksums for 9.2