David G Johnston wrote
> On Saturday, December 20, 2014, Mike Pultz [via PostgreSQL] <
> ml-node+s1045698n5831551h5@.nabble
>> wrote:
>
>> Hey David,
>>
>> > What version are you using?
>>
>> Sorry, I'm on 9.3.4.
>>
>> >Now() is a volatile function so the planner cannot omit partitions.
>> >
>>
On Saturday, December 20, 2014, Mike Pultz [via PostgreSQL] <
ml-node+s1045698n583155...@n5.nabble.com> wrote:
> Hey David,
>
> > What version are you using?
>
> Sorry, I'm on 9.3.4.
>
> >Now() is a volatile function so the planner cannot omit partitions.
> >
> >Replace that with a constant and no
Hey David,
> What version are you using?
Sorry, I'm on 9.3.4.
>Now() is a volatile function so the planner cannot omit partitions.
>
>Replace that with a constant and now it can.
I'm not sure what you mean- now() is a stable function:
cloud_test2=# \df+ now()
Schema | Name | Result d
Mike Pultz wrote
> Is there something I'm missing?
What version are you using?
Now() is a volatile function so the planner cannot omit partitions.
Replace that with a constant and now it can.
David J.
--
View this message in context:
http://postgresql.nabble.com/Problem-with-constraint-exc
Hello,
I'm having an issue getting the query planner to skip child tables based on
my check constraints. I have
constraint_exclusion = partition
in my config file, and I think I have everything set up correctly.
The parent table shows the child tables:
cloud_test2=# \d+ engine_
