Am 31.07.2006 um 19:08 schrieb Michael Stone:
> I never saw a column description--that would certainly help. :) I
> saw a schema, but not an explanation of what the elements do. From
> what I can understand of what you're saying, it is sounding as
> though the bacula.file table contains an entry for the subdirectory
> itself as well as entries for each file in the subdirectory?
It is the junction relation between path and filename and job and
1. which files (identified by bacula.filename) are in a directory
(identified by bacula.path)
2. For each of those files they record a snapshot with
characteristics (lstat [base64 encoded], md5-checksum and a backup-
job [via jobid], which itself has backup-time etc.)
> And the reason you need to join back to the filename table is that
> there may be multiple copies of the filename from multiple backups?
One entry per backup(job) for each bacula.path/bacula.filename pair
> Does the subdirectory itself have an entry in the filename table?
Yes. Directories reference an entry containing '' in
> What is the content of the lstat column
File status info -- see stat(2).
> ; can it be used to distinguish a file from a directory?
Yes, the S_IFDIR bit identifies directories, but the whole lstat
column is base64 encoded
> Similarly for the md5 column--what would it contain for a directory?
It seems to contain 0.
Axel Rau, ☀Frankfurt , Germany +49-69-951418-0
In response to
pgsql-performance by date
|Next:||From: Bruce Momjian||Date: 2006-07-31 19:57:03|
|Subject: Re: Performances with new Intel Core* processors|
|Previous:||From: Michael Stone||Date: 2006-07-31 17:08:36|
|Subject: Re: directory tree query with big planner variation|