On Thu, Feb 18, 2010 at 7:46 AM, Nahuel ANGELINETTI
wrote:
> Hi,
>
> Le 18/02/2010 13:42, Galen Charlton a écrit :
>>
>> Hi,
>>
>> On Thu, Feb 18, 2010 at 6:47 AM, Chris Nighswonger
>> wrote:
>>
including not freeing space in the file system even if you truncate the
table :(
On 18/02/10 12:42, Galen Charlton wrote:
> However, reclaiming space is easy enough, since by default a separate
> InnoDB file is created for each table: just drop and recreate the
> sessions table. You can also use MyISAM instead of InnoDB for that
> table.
I'm not sure it is the default. It req
Hi,
On Thu, Feb 18, 2010 at 7:45 AM, Colin Campbell
wrote:
> If you have everything in one ibdata file it can be difficult to recover
> space.
Yes, that's why is a good idea to use a separate file for each InnoDB
table; you can enable this by turning on the innodb_file_per_table
option in the My
Hi,
Le 18/02/2010 13:42, Galen Charlton a écrit :
> Hi,
>
> On Thu, Feb 18, 2010 at 6:47 AM, Chris Nighswonger
> wrote:
>
>>> including not freeing space in the file system even if you truncate the
>>> table :(
>>>
>> Ouch! this would seem to be a mysql bug. Is there no way to ensure
On 18/02/10 11:47, Chris Nighswonger wrote:
> On Thu, Feb 18, 2010 at 5:05 AM, Paul Poulain
> wrote:
>> Le 17/02/2010 21:10, Chris Cormack a écrit :
>>> 2010/2/18 Clay Fouts:
>>>
It depends, actually. For tables without FK constraints (like Koha's
"sessions"), truncation is instantaneou
Hi,
On Thu, Feb 18, 2010 at 6:47 AM, Chris Nighswonger
wrote:
>> including not freeing space in the file system even if you truncate the
>> table :(
>
> Ouch! this would seem to be a mysql bug. Is there no way to ensure the
> drive space is freed up?
It's an issue with the InnoDB storage engine,
On Thu, Feb 18, 2010 at 5:05 AM, Paul Poulain wrote:
> Le 17/02/2010 21:10, Chris Cormack a écrit :
>> 2010/2/18 Clay Fouts :
>>
>>> It depends, actually. For tables without FK constraints (like Koha's
>>> "sessions"), truncation is instantaneous in MySQL.
>>>
>>>
>> Not when they tried it yesterd
Le 17/02/2010 21:10, Chris Cormack a écrit :
> 2010/2/18 Clay Fouts :
>
>> It depends, actually. For tables without FK constraints (like Koha's
>> "sessions"), truncation is instantaneous in MySQL.
>>
>>
> Not when they tried it yesterday :-)
>
> It does depend, InnoDB can do some strange t
Definitely. Even though the session table may in many cases be much smaller
than other tables in terms of bytes or rows, the frequency at which it is
written to causes it to be heavily fragmented on the disk, which greatly
reduces the average throughput during a mysqldump, increasing the backup
tim
n...@lists.koha.org] *On Behalf Of *Clay Fouts
> *Sent:* Wednesday, February 17, 2010 2:04 PM
> *To:* Koha-devel
> *Subject:* Re: [Koha-devel] Koha sessions table is ridiculously huge
>
>
>
> You can also use "truncate sessions" to do the job if you just want to
> cl
And since you must backup daily your Koha DB, you should truncate
sessions table just before mysqldump-ing in order to backup as few
sessions data as possible.
--
Frédéric
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mail
2010/2/18 Clay Fouts :
> It depends, actually. For tables without FK constraints (like Koha's
> "sessions"), truncation is instantaneous in MySQL.
>
Not when they tried it yesterday :-)
It does depend, InnoDB can do some strange things.
Chris
___
Koha-d
It depends, actually. For tables without FK constraints (like Koha's
"sessions"), truncation is instantaneous in MySQL.
On Wed, Feb 17, 2010 at 12:02 PM, Chris Cormack wrote:
> 2010/2/18 Clay Fouts :
> > You can also use "truncate sessions" to do the job if you just want to
> clear
> > out the c
2010/2/18 Clay Fouts :
> You can also use "truncate sessions" to do the job if you just want to clear
> out the contents of the table. It's faster and simpler than using mysqldump.
>
> This issue arises from the fact that the way Koha is written, if a user just
> walks away from a session without l
Hi,
2010/2/17 Clay Fouts :
> You can also use "truncate sessions" to do the job if you just want to clear
> out the contents of the table. It's faster and simpler than using mysqldump.
Also, in HEAD there's a little script to truncate sessions as well as
get rid of old zebraqueue entries. It's c
ehalf Of Clay Fouts
Sent: Wednesday, February 17, 2010 2:04 PM
To: Koha-devel
Subject: Re: [Koha-devel] Koha sessions table is ridiculously huge
You can also use "truncate sessions" to do the job if you just want to clear
out the contents of the table. It's faster and simpler than u
You can also use "truncate sessions" to do the job if you just want to clear
out the contents of the table. It's faster and simpler than using mysqldump.
This issue arises from the fact that the way Koha is written, if a user just
walks away from a session without logging out, their session data w
Developers,
After performing a software upgrade and server reboot, I came across this
problem. My koha.sessions table is over 13 million entries. This seems to
indicate that entries into the table were never removed, and that may help to
explain why my backup mysqldumps are increasing by aro
18 matches
Mail list logo
