Re: Limiting setting of hint bits by read-only queries; vacuum_delay

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Limiting setting of hint bits by read-only queries; vacuum_delay
Date: 2013-03-26 17:07:08
Message-ID: 20130326170708.GE20871@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 26, 2013 at 03:06:30PM +0000, Simon Riggs wrote:
> > More generally, the fact that a patch has some user-frobbable knob
> > does not mean that it's actually a good or even usable solution. As
> > everybody keeps saying, testing on a wide range of use-cases would be
> > needed to prove that, and we don't have enough time left for such
> > testing in the 9.3 timeframe. This problem needs to be attacked in
> > an organized and deliberate fashion, not by hacking something up under
> > time pressure and shipping it with minimal testing.
>
> Well, it has been tackled like that and we've *all* got nowhere. No
> worries, I can wait a year for that beer.

This was the obvious result of this discussion --- it is a shame we had
to discuss this rather than working on more pressing 9.3 issues. I also
think someone saying "I would like to apply this now" is more disruptive
than casual discussion about things like buffer count locking.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Darren Duncan 2013-03-26 17:14:35 Re: adding support for zero-attribute unique/etc keys
Previous Message Merlin Moncure 2013-03-26 16:48:09 Re: Page replacement algorithm in buffer cache