Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Mladen Gogala Newsgroups: comp.databases.postgresql Subject: Re: pg_hint_plan Date: Mon, 16 Feb 2015 14:59:25 +0000 (UTC) Organization: A noiseless patient Spider Lines: 21 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Mon, 16 Feb 2015 14:59:25 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="9dbb49b777b4f27f09e09421fc52f8c8"; logging-data="3254"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19q+AJleZSpkHit4VjWoSL9" User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) Cancel-Lock: sha1:GBCbnnV++2bG8imuGwGwuFgZY94= Xref: csiph.com comp.databases.postgresql:634 On Mon, 16 Feb 2015 15:24:24 +0100, Dimitri Fontaine wrote: > Again, as soon as you use hints, then you need to review every once in a > while that they are still effective, because they won't be re-evaluated > against data growth as the usual PostgreSQL statistics system are. Also > each new version of PostgreSQL will come with a better planner and > optimiser, so you will need to review all hints and remove the rotted > ones. Yes, hints rot. Yes, they indeed do rot. As I have said in my post, hints are only a fire fighting solution of the last resort. And they are necessary as such. My deepest gratitude goes to the author(s) of the extension who have made them available. -- Mladen Gogala The Oracle Whisperer http://mgogala.byethost5.com Je suis Charlie