Re: Partitions not Working as Expected
| От | Dave Johansen |
|---|---|
| Тема | Re: Partitions not Working as Expected |
| Дата | |
| Msg-id | CAAcYxUfCaYbpAv-sQaNGKEVK2UZA1BtL87jM8LBd81ZomaLUuA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Partitions not Working as Expected (bricklen <bricklen@gmail.com>) |
| Ответы |
Re: Partitions not Working as Expected
|
| Список | pgsql-performance |
On Thu, Jun 27, 2013 at 10:34 AM, bricklen <bricklen@gmail.com> wrote:
On Thu, Jun 27, 2013 at 10:17 AM, Shaun Thomas <sthomas@optionshouse.com> wrote:
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.Would it help to put the current_date call in a wrapper function and coerce it as IMMUTABLE? A quick test shows that constraint exclusion seems to kick in, but I can't speak intelligently about whether that is wise or not.
Or what about something like DATE_TRUNC("DAY", now())? Or would that run into the same optimization/planner problems as CURRENT_DATE?
В списке pgsql-performance по дате отправления: