| From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
|---|---|
| To: | Igor Neyman <ineyman(at)perceptron(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Partitions not Working as Expected |
| Date: | 2013-06-27 17:17:42 |
| Message-ID: | 51CC73B6.2050406@optionshouse.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 06/27/2013 12:08 PM, Igor Neyman wrote:
> Doesn't have to be hardcoded.
> If executed as dynamic sql, it will be re-planned properly, e.g.:
Well yeah. That's not really the point, though. Aside from existing
code, hard-coding is generally frowned upon. Our devs have been using
CURRENT_DATE and its ilk for over six years now.
So now I get to tell our devs to refactor six years of JAVA code and
find any place they use CURRENT_DATE, and replace it with an ORM
variable for the current date instead.
At this point I wonder why CURRENT_DATE even exists, if using it is
apparently detrimental to query execution.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
sthomas(at)optionshouse(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | bricklen | 2013-06-27 17:34:30 | Re: Partitions not Working as Expected |
| Previous Message | Igor Neyman | 2013-06-27 17:08:43 | Re: Partitions not Working as Expected |