| From: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Johnston <polobo(at)yahoo(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Planner hints in Postgresql |
| Date: | 2014-03-17 22:27:14 |
| Message-ID: | 532776C2.4050905@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/17/2014 11:15 PM, Josh Berkus wrote:
> 2. they eventually become a barrier to upgrading, once the performance
> of the DB engine changes in a way that makes older query decorators
> crippling and/or erroneous. Because they are scattered all around the
> code, it then becomes a major refactoring effort to fix them.
My idea of associating them with major versions and issuing warnings
would help with this.
> 5. Application developers will add them without telling the DBAs, and
> vice-versa. Hilarity ensues.
And this would be unmasked at next major upgrade when the logs fill up.
--
Vik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2014-03-17 22:40:37 | Re: Planner hints in Postgresql |
| Previous Message | Vik Fearing | 2014-03-17 22:18:53 | Re: Planner hints in Postgresql |