I tried the partitioning scenario but I've got into
the same problem. The max function is not using the
indexes on the two partitioned tables...
Any other thoughts?
--- Ioana Danes <ioanasoftware(at)yahoo(dot)ca> wrote:
> Thanks a lot I will give it a try.
> --- Dimitri Fontaine <dim(at)dalibo(dot)com> wrote:
> > Hi,
> > Le mercredi 18 octobre 2006 21:51, Ioana Danes a
> > écrit :
> > > I am doing a test for a scenario where I have 2
> > > schemas one (public) for the operational data
> > > another one (archive) for old, archived data. So
> > > basically I want to split the data from some
> > > tables in two. All data before 2006 in archive
> > all
> > > data after and including 2006 in public.
> > [...]
> > > I got into a scenario where my plan does not
> > > without doing code change.
> > This sounds a lot as a ddl partitionning, you may
> > want to add some checks to
> > your schema and set constraint_exclusion to on in
> > your postgresql.conf.
> > Please read following documentation material :
> > Regards,
> > --
> > Dimitri Fontaine
> > http://www.dalibo.com/
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam
> protection around
> ---------------------------(end of
> TIP 3: Have you checked our extensive FAQ?
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
In response to
pgsql-performance by date
|Next:||From: Jeff Davis||Date: 2006-10-18 21:07:28|
|Subject: Re: Postgresql 8.1.4 - performance issues for select on|
|Previous:||From: Larry Rosenman||Date: 2006-10-18 20:59:22|
|Subject: Re: [PERFORM] autovacuum on a -mostly- r/o table|