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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Limiting setting of hint bits by read-only queries; vacuum_delay
Date: 2013-03-24 13:38:15
Message-ID: 24890.1364132295@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> Can we do this now?

No.

We are trying to get 9.3 out the door, not undertake design, coding,
and testing of entirely new behaviors which will have complex
performance tradeoffs. This sounds like a great project for early in
the 9.4 development cycle, but it's way too late to try to do it now.
(At least if you'd like to ship 9.3 this year. If we're going to
re-open 9.3 for this kind of development, I have some planner fixes
I need to make ...)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2013-03-24 14:26:12 Re: Let's invent a function to report lock-wait-blocking PIDs
Previous Message Greg Stark 2013-03-24 13:29:55 Re: Limiting setting of hint bits by read-only queries; vacuum_delay