[rt-users] Need to decode session data or session id information

[Ruslan Zakirov]

Hello Dan,

The script you're looking for is part of RT-Extensions-Utils, but I
know what in those sessions. Some of your users searched for tickets
and RT found too many of them, so there is now big map for 'first',
'next', 'prev' and 'last' links in the session. RT 3.8.8 has really
good improvement in that area, we now store only part of the map and
size of the map can be controlled from the RT config.

I would suggest you to test RT 3.8.8 RC3 to make sure there is no
regressions that will stop you from upgrading to RT 3.8.8.

On Wed, Apr 21, 2010 at 9:53 PM, Dan O'Neill <rt at northpb.com> wrote:
> Hi,
>
> We're using RT 3.8.4 and on several occasions RT is storing session data
> that is extremely large.  Here is a query from our system this morning.
>
> rt3=# select lastupdated, length(a_session) from sessions where lastupdated
>>= '2010-04-21' order by  length(a_session) desc limit 3;
>        lastupdated         |  length
> ----------------------------+----------
>  2010-04-21 13:29:15.175317 | 99067236
>  2010-04-21 06:17:13.315054 |   369098
>  2010-04-21 17:31:02.568494 |    59882
> (3 rows)
>
> Can someone provide me with a snippet of code that can decode and dump the
> session id or the a_session data block so that I can figure out who or what
> is causing this to occur?
>
> Thanks,
>
> Dan
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>



-- 
Best regards, Ruslan.