Bacula-users

Re: [Bacula-users] decoding lstat data

2009-04-15 14:10:14
Subject: Re: [Bacula-users] decoding lstat data
From: "Kelly, Brian" <Brian.Kelly AT uwsp DOT edu>
To: Craig Ringer <craig AT postnewspapers.com DOT au>
Date: Wed, 15 Apr 2009 13:04:25 -0500
If I run my example query against the backup with the largest volume of files 
163222 it takes 28 secs.

Brian

-----Original Message-----
From: Craig Ringer [mailto:craig AT postnewspapers.com DOT au]
Sent: Tuesday, April 14, 2009 10:23 PM
To: Kelly, Brian
Cc: bacula-users AT lists.sourceforge DOT net
Subject: Re: [Bacula-users] decoding lstat data

Kelly, Brian wrote:
> I've seen lots of posts regarding the decoding of Lstat data. I'm currently
> using a few functions to decoded the lstat data and make it human readable.
> These functions have been tested and are known to work with mysql 5.0.70

> CREATE FUNCTION MYBASE64_DECODE (input BLOB)

Isn't that .... slow?

> END |

> In this particular
> situation it's too bad the MIME type for each file isn't stored in the
> catalog.

Bacula can't store the MIME type, because it doesn't know the MIME type
of the files its storing. It only knows what the file system knows, and
few (if any) file systems keep track of MIME types.

--
Craig Ringer

Attachment: smime.p7s
Description: S/MIME cryptographic signature

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>