Re: Parameterized paths vs index clauses extracted from OR clauses
От | Craig Ringer |
---|---|
Тема | Re: Parameterized paths vs index clauses extracted from OR clauses |
Дата | |
Msg-id | 51354614.7070300@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: Parameterized paths vs index clauses extracted from OR clauses (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
<div class="moz-cite-prefix">On 03/05/2013 12:33 AM, Robert Haas wrote:<br /></div><blockquote cite="mid:CA+TgmoZoRySYSvrSYLbiR3eCYgWAaZzPNHr+2vAq7JWFqF2f+Q@mail.gmail.com"type="cite"><pre wrap="">On Thu, Feb 28, 2013at 3:03 PM, Tom Lane <a class="moz-txt-link-rfc2396E" href="mailto:tgl@sss.pgh.pa.us"><tgl@sss.pgh.pa.us></a> wrote: </pre><blockquote type="cite"><pre wrap="">Whichever way we go, the resulting patch is likely to be too large and invasive for me to feel terribly comfortable about back-patching it into 9.2. AFAICT this issue only arises for indexquals extracted out of larger OR conditions, so maybe it's not worth taking such a risk for. </pre></blockquote><pre wrap=""> EnterpriseDB has received a number of complaints from our customers resulting from planner behavior changes which were back-patched; so I am not sanguine about back-patching unless the situation is pretty darn dire and the fix is pretty darn near certain to be an improvement in every case. As we have discussed many times here and on pgsql-performance, DBAs seem to prefer a query plan that's the same every time, even if it's bad. Updating to get a security fix and having plans change under you proves to be an unpleasant surprise.</pre></blockquote> It also weakens our argument (per versioningpolicy) that patch releases are *totally safe* and are something you can apply without extensive testing and QAper <a href="http://www.postgresql.org/support/versioning/">http://www.postgresql.org/support/versioning/</a> .<br /><br/> I have enough trouble getting people to update as it is.<br /><br /> I'd be interested in being able to turn on fixes/enhancements,but having behaviour changes that aren't clear wins in all cases turned on by default seems likely toweaken trust from users who're already way too leery of updating.<br /><br /><pre class="moz-signature" cols="72">-- CraigRinger <a class="moz-txt-link-freetext" href="http://www.2ndQuadrant.com/">http://www.2ndQuadrant.com/</a>PostgreSQLDevelopment, 24x7 Support, Training & Services</pre>
В списке pgsql-hackers по дате отправления: