[rt-users] How to avoid a huge dataset returning

[Kevin Falcone]

On Fri, Sep 16, 2011 at 09:02:36PM +0300, Michael Stepanov wrote:
>    I use RT 3.8.2

That still doesn't look like a standard RT query.
You'll need to move on to my other suggestion.

>      your version. You'll probably want to turn on the StatementLog option
>      and figure out where that query is coming from so you can fix the
>      source.

-kevin


>    On Fri, Sep 16, 2011 at 6:02 PM, Kevin Falcone <[1]falcone at bestpractical.com> wrote:
> 
>      On Fri, Sep 16, 2011 at 05:08:24PM +0300, Michael Stepanov wrote:
>      > Hi,
>      >
>      > Our RT3 system is a big and it crashes time to time. Today we found one
>      > query in the slow queries log which killed the system:
>      > *
>      > # Query_time: 97 Lock_time: 0 Rows_sent: 15906633 Rows_examined: 39069181
>      > SELECT main.* FROM Transactions main WHERE (main.Type = 'Create' OR
>      > main.Type = 'Comment' OR main.Type = 'Correspond') ORDER BY main.Created
>      > ASC, [2]main.id ASC;
>      > *
>      > Is there a way to reduce a number of returning records on the application
>      > level?
> 
>      That doesn't looks like a standard RT query, but you haven't provided
>      your version. You'll probably want to turn on the StatementLog option
>      and figure out where that query is coming from so you can fix the
>      source.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20110916/bea76a88/attachment.sig>