On 2/28/10 1:51 PM, Kenneth Marshall wrote:
> On Sun, Feb 28, 2010 at 12:29:14PM -0800, Josh Berkus wrote:
>>> However the same query against the base table when specifying the check
>>> constraint key in the where clause produces sequential scans:
>> Does the "master" table have the same indexes
On Sun, Feb 28, 2010 at 12:29:14PM -0800, Josh Berkus wrote:
>
> > However the same query against the base table when specifying the check
> > constraint key in the where clause produces sequential scans:
>
> Does the "master" table have the same indexes as the slave partitions?
>
> --Josh Berk
> However the same query against the base table when specifying the check
> constraint key in the where clause produces sequential scans:
Does the "master" table have the same indexes as the slave partitions?
--Josh Berkus
--
Sent via pgsql-performance mailing list (pgsql-performance@postgres
On Wednesday 24 February 2010 07:55:36 A. Kretschmer wrote:
> In response to Kevin Kempter :
> > Hi All;
> >
> > I have a table that has daily partitions.
> >
> > The check constraints look like this:
> > CHECK (timezone('EST'::text, insert_dt) >= '2010-01-01'::date
> > AND timezone('EST'::text, in
In response to Kevin Kempter :
> Hi All;
>
> I have a table that has daily partitions.
>
> The check constraints look like this:
> CHECK (timezone('EST'::text, insert_dt) >= '2010-01-01'::date
> AND timezone('EST'::text, insert_dt) < '2010-01-02'::date)
>
> each partition has this index:
>
Hi All;
I have a table that has daily partitions.
The check constraints look like this:
CHECK (timezone('EST'::text, insert_dt) >= '2010-01-01'::date
AND timezone('EST'::text, insert_dt) < '2010-01-02'::date)
each partition has this index:
"fact_idx1_20100101_on_cust_id" btree (cust_id)
I
