Hello Eric,
this patch solves the mysql problems.
Very good, it runs smoothly even on my slow machine, which before ran for more
than 40 hours now is ready in a few seconds.
Excellent!
Am Montag 22 Februar 2010 17:51:54 schrieb Eric Bollengier:
> Le Lundi 22 Février 2010 15:34:07, Philipp Sto
Le Lundi 22 Février 2010 15:34:07, Philipp Storz a écrit :
> Hello Eric,
>
> the second patch changes nothing in the behaviour:
>
> The mysql query lasts exaclty as long as before, and there is no error.
Hi Philipp,
I have corrected the small mistake in the first patch, could you try it ?
Thank
Hello Eric,
the second patch changes nothing in the behaviour:
The mysql query lasts exaclty as long as before, and there is no error.
regards,
Philipp
Am Montag 22 Februar 2010 10:26:48 schrieb Eric Bollengier:
> Hi Philipp,
>
> Le Lundi 22 Février 2010 09:34:02, Philipp Storz a écrit :
> >
Hello Eric,
the first patch does not work correctly:
It produces this error:
Query failed: DROP TABLE new_basefile7: ERR=Unknown table 'new_basefile7'
[---logfile---]
22-Feb 14:40 bacula-old-fd JobId 7: Space saved with Base jobs: 0 MB
22-Feb 14:40 bacula-sd JobId 7: Job write elapsed time =
Hi Philipp,
Le Lundi 22 Février 2010 09:34:02, Philipp Storz a écrit :
> Hello Eric,
>
> how can we go on to solve the problem with mysql and base jobs?
Good question, as it's quite hard to know where is the performance
problem (i'm not able to read and understand the explain output), it could
Hello Eric,
how can we go on to solve the problem with mysql and base jobs?
Like it behaves now, it is unusable. Unfortunately, I do not have much skills
in database tuning, but there has to be a big problem for mysql with the
mentinoned INSERT:
INSERT INTO BaseFiles (BaseJobId, JobId, FileId
Hi,
This index was giving this result on postgres and sqlite
http://sourceforge.net/apps/wordpress/bacula/2009/09/28/performance-issue-with-a-useless-index-on-postgresql/
It should do the same with MySQL...
Bye
Le Dimanche 21 Février 2010 10:00:35, Philipp Storz a écrit :
> Update:
>
> I trie
Update:
I tried the suggestion posted by Dan Langille
(CREATE INDEX FilenameId_2 ON File (FilenameId, PathId);)
,but unfortunately this did not help in my case.
regards,
Philipp
Am 17.02.2010 15:31, schrieb Philipp Storz:
> Hello,
>
> I did some more testing, and the problem still exists also
Hello,
I did some more testing, and the problem still exists also on the following
MySql Versions:
* 5.1.37, for debian-linux-gnu on
* mysql 5.5.1-m2 from the mysql website on SLES11-64Bits
Am Mittwoch 17 Februar 2010 09:17:22 schrieb Philipp Storz:
> Hello,
>
> I startet testing base jobs,
Hello,
I startet testing base jobs, and I found a very strange behaviour on mysql,
while on postgres everything seems to be fine:
What I did:
I configured one base job, and a "normal" job which depends on this base job:
On a freshly installed and created mysql database, I first ran the base jo
10 matches
Mail list logo