Anj Adu writes:
> This query is doing a sequential scan on the child partitions even
> though indexes on all constrained columns are present
It looks to me like it's doing exactly what it is supposed to, ie,
indexscan on the partitions where it would help and seqscans on the
partitions where it w
Hi
This query is doing a sequential scan on the child partitions even
though indexes on all constrained columns are present
The box is very lightly loaded (8 core 15K 6x300G Raid 10 disks)
explain analyze
select thedate,sent.theboxid_id,sub_box_id,box_num,sum(summcount) as
event_count,'ACC'
2009/10/14 Scott Marlowe
> On Wed, Oct 14, 2009 at 1:20 AM, Pavel Stehule
> wrote:
> > 2009/10/14 Thom Brown :
> >> 2009/10/14 Scott Marlowe :
> >> Why not just do something like:
> >>
> >> SELECT thisfield, thatfield
> >> FROM my_table
> >> WHERE thisfield IS NOT NULL
> >> ORDER BY RANDOM()
> >
On Wed, Oct 14, 2009 at 1:20 AM, Pavel Stehule wrote:
> 2009/10/14 Thom Brown :
>> 2009/10/14 Scott Marlowe :
>>>
>>> If what you're trying to do is emulate a real world app which randomly
>>> grabs rows, then you want to setup something ahead of time that has a
>>> pseudo random order and not rel
2009/10/14 Thom Brown :
> 2009/10/14 Scott Marlowe :
>>
>> If what you're trying to do is emulate a real world app which randomly
>> grabs rows, then you want to setup something ahead of time that has a
>> pseudo random order and not rely on using anything like order by
>> random() limit 1 or anyth
