pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ramesh kumar <mbrameshkumar@gmail.com>
To: Matteo Beccati <php@beccati.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: ORDER BY and LIMIT not propagated on inherited
Date: Sat, 3 Sep 2005 01:38:53 +0530
Message-ID: <bda43614050902130816116052@mail.gmail.com> (raw)
In-Reply-To: <43189B0F.2000904@beccati.com>
References: <43182789.4070307@beccati.com>
	<1125683697.3956.310.camel@localhost.localdomain>
	<43189B0F.2000904@beccati.com>

Hi all
I have got lot of information from ur group.
Now i want to relieve from this group.
I kindly request all of you.
Plz unsubcribe me.
Thankz a lot
Ramesh

 On 9/3/05, Matteo Beccati <php@beccati.com> wrote: 
> 
> Simon Riggs wrote:
> > Returning to Matteo's original query, what we are saying is that the new
> > optimization for MIN/MAX queries doesn't work with inherited tables.
> >
> > It could do, by running optimize_minmax_aggregates() for each query that
> > gets planned to see if a better plan exists for each child table.
> >
> > I think that's a TODO item.
> 
> Great. Of course I'm using ORDER BY ... LIMIT as a workaround to get the
> index scan on pre-8.1, and because I'm used to it insted of the
> previously not optimized MIN/MAX aggregates.
> 
> > Optimizing ORDER BY and LIMIT down looks like it would be harder to do
> > in the general case, even if Matteo's simple transform looks good. I'm
> > not sure it's a very common query type though...
> 
> If I can find some time, I'll try to write some hacks... I just need to
> find out where to start ;)
> 
> 
> Best regards
> --
> Matteo Beccati
> http://phpadsnew.com/
> http://phppgads.com/
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
> 



-- 
urs

RameshKumar.M

view thread (9+ messages)

Message-ID: <bda43614050902130816116052@mail.gmail.com>
Permalink:  ../bda43614050902130816116052@mail.gmail.com/
Also on:    postgresql.org/message-id/bda43614050902130816116052@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: mbrameshkumar@gmail.com, php@beccati.com, simon@2ndquadrant.com
  Subject: Re: ORDER BY and LIMIT not propagated on inherited
  In-Reply-To: <bda43614050902130816116052@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox