Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 29E299FB2E6 for ; Wed, 18 Oct 2006 18:02:06 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 28902-09 for ; Wed, 18 Oct 2006 18:02:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from web55907.mail.re3.yahoo.com (web55907.mail.re3.yahoo.com [216.252.110.68]) by postgresql.org (Postfix) with SMTP id CF94E9FB2CC for ; Wed, 18 Oct 2006 18:02:02 -0300 (ADT) Received: (qmail 56437 invoked by uid 60001); 18 Oct 2006 21:02:01 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=I+Oxvv/+P3GOZ/Qh5l9TCmAd/KWut7733mM9zIQ3Wpi2m3bv2sHh5U6vnIB+zArFIdilnStGfVjj3tI2TcvF4bJmycNgpHJb47oUgr6jmTe7L8gEynlz16yGVhv4vNMfkVAaTvuW+4jqy2c0cEIKAbA4OmHWNmH64DZDXnXJBY8= ; Message-ID: <20061018210201.56435.qmail@web55907.mail.re3.yahoo.com> Received: from [207.164.182.8] by web55907.mail.re3.yahoo.com via HTTP; Wed, 18 Oct 2006 17:02:01 EDT Date: Wed, 18 Oct 2006 17:02:01 -0400 (EDT) From: Ioana Danes Subject: Re: Postgresql 8.1.4 - performance issues for select on view using max To: Ioana Danes , Dimitri Fontaine , pgsql-performance@postgresql.org Cc: Ioana Danes In-Reply-To: <20061018203434.21060.qmail@web55905.mail.re3.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.201 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE X-Spam-Level: X-Archive-Number: 200610/374 X-Sequence-Number: 21503 Hello, 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 wrote: > Thanks a lot I will give it a try. > > --- Dimitri Fontaine 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 > and > > > another one (archive) for old, archived data. So > > > basically I want to split the data from some > huge > > > tables in two. All data before 2006 in archive > and > > all > > > data after and including 2006 in public. > > [...] > > > I got into a scenario where my plan does not > work > > > 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 : > > > > > http://www.postgresql.org/docs/8.1/interactive/ddl-partitioning.html > > > > Regards, > > -- > > Dimitri Fontaine > > http://www.dalibo.com/ > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > > ---------------------------(end of > broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com