On 10/19/09 12:10 PM, "Robert Haas" wrote:
> 2009/10/19 Grzegorz Jaśkiewicz :
>>
>>
>> 2009/10/19 Robert Haas
>>>
>>> 2009/10/19 Grzegorz Jaśkiewicz :
On Sun, Oct 11, 2009 at 3:30 PM, Michal Szymanski
wrote:
>
> We have similar problem and now we are try to f
2009/10/19 Grzegorz Jaśkiewicz :
>
>
> 2009/10/19 Robert Haas
>>
>> 2009/10/19 Grzegorz Jaśkiewicz :
>> >
>> >
>> > On Sun, Oct 11, 2009 at 3:30 PM, Michal Szymanski
>> > wrote:
>> >>
>> >> We have similar problem and now we are try to find solution. When you
>> >> execute query on partion there
Joe Uhl wrote:
This seems like a pretty major weakness in PostgreSQL partitioning. I
have essentially settled on not being able to do queries against the
parent table when I want to order the results. Going to have to use a
Hibernate interceptor or something similar to rewrite the statements
2009/10/19 Robert Haas
> 2009/10/19 Grzegorz Jaśkiewicz :
> >
> >
> > On Sun, Oct 11, 2009 at 3:30 PM, Michal Szymanski
> > wrote:
> >>
> >> We have similar problem and now we are try to find solution. When you
> >> execute query on partion there is no sorting - DB use index to
> >> retrieve dat
2009/10/19 Grzegorz Jaśkiewicz :
>
>
> On Sun, Oct 11, 2009 at 3:30 PM, Michal Szymanski
> wrote:
>>
>> We have similar problem and now we are try to find solution. When you
>> execute query on partion there is no sorting - DB use index to
>> retrieve data and if you need let say 50 rows it reads
On Sun, Oct 11, 2009 at 3:30 PM, Michal Szymanski wrote:
> We have similar problem and now we are try to find solution. When you
> execute query on partion there is no sorting - DB use index to
> retrieve data and if you need let say 50 rows it reads 50 rows using
> index. But when you execute on
This seems like a pretty major weakness in PostgreSQL partitioning. I
have essentially settled on not being able to do queries against the
parent table when I want to order the results. Going to have to use a
Hibernate interceptor or something similar to rewrite the statements so
they hit spe
I've described our problem here
http://groups.google.pl/group/pgsql.performance/browse_thread/thread/54a7419381bd1565?hl=pl#
Michal Szymanski
http://blog.szymanskich.net
http://techblog.freeconet.pl/
--
Sent via pgsql-performance mailing list ([email protected])
To make changes t
We have similar problem and now we are try to find solution. When you
execute query on partion there is no sorting - DB use index to
retrieve data and if you need let say 50 rows it reads 50 rows using
index. But when you execute on parent table query optymizer do this:
-> Sort (cost=726844.88
