| From: | "Amit Langote" <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | "'Robert Haas'" <robertmhaas(at)gmail(dot)com> |
| Cc: | "'Alvaro Herrera'" <alvherre(at)2ndquadrant(dot)com>, "'Claudio Freire'" <klaussfreire(at)gmail(dot)com>, "'Josh Berkus'" <josh(at)agliodbs(dot)com>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Pg Hackers'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: On partitioning |
| Date: | 2014-12-15 23:55:35 |
| Message-ID: | 00cb01d018c2$9eb97260$dc2c5720$@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert wrote:
> On Sun, Dec 14, 2014 at 9:12 PM, Amit Langote
> <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> > This means if a user puts arbitrary expressions in a partition definition, say,
> >
> > ... FOR VALUES extract(month from current_date) TO extract(month from
> current_date + interval '3 months'),
> >
> > we make sure that those expressions are pre-computed to literal values.
>
> I would expect that to fail, just as it would fail if you tried to
> build an index using a volatile expression.
Oops, wrong example, sorry. In case of an otherwise good expression?
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2014-12-16 00:00:53 | Re: Join push-down support for foreign tables |
| Previous Message | Michael Paquier | 2014-12-15 23:39:51 | Re: Status of CF 2014-10 and upcoming 2014-12 |