hyelluas writes:
> You are right to the point, Tom.
> The datex is timestamp with time zone and the constraints were created as
> timestamp without time zone.
> As soon as I fixed that , it all started working.
OK. In case anybody is wondering *why* that fixed it: a comparison
between timestamp
You are right to the point, Tom.
The datex is timestamp with time zone and the constraints were created as
timestamp without time zone.
As soon as I fixed that , it all started working.
thank you!
Helen
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/constraint-partition
hyelluas writes:
> sorry, my table has many columns and missed the datex when make it look
> smaller.
> datex is the column in the table. This is the driving constraint.
> My task is to have 30 days of data with 5mln to 10 mln rec in 1 hour table,
> so I partition it by hour table and combine the
sorry, my table has many columns and missed the datex when make it look
smaller.
datex is the column in the table. This is the driving constraint.
My task is to have 30 days of data with 5mln to 10 mln rec in 1 hour table,
so I partition it by hour table and combine them into days, which are
combi
writes:
> CREATE TABLE summary_total
> (
> counter bigint DEFAULT 0,
> destgeo_id integer DEFAULT 1,
> direction integer DEFAULT 1,
> mlapp_id integer DEFAULT 1
> )
> CREATE TABLE summary_daily_data
> (
> )
> INHERITS (summary_total)
> CREATE TABLE summ_dly_1505500
> (
> )
> INHERITS (su
Please help me understanding this execution plan :
I have a table and 3 levels of partitions .
All the tables on second level have date constraints.
Execution plan shows that all partitions are checked by the optimizer,
Nothing is excluded. My test example worked fine but this one does not.
Tha
