> It'd be really nice if Bacula could store this information in a more
> query-friendly way.
Oh, as a follow-up to my prior post:
For what it's worth, in PostgreSQL the amount of storage required to
store the lstat information as individual int4 fields is almost exactly
the same as what's needed
> It'd be really nice if Bacula could store this information in a more
> query-friendly way.
Just for kicks, I've written an extension to PostgreSQL that lets you
decode the lstat field into a proper `stat' structure you can query,
build indexes on, etc. It's basically just a PostgreSQL function
Foo wrote:
> Hi,
>
> I'm looking to mod query option 12 to list not just path/filename but size
> too, possibly other attributes like permissions, datestamps etc.
>
> Is this info kept in the catalog somewhere or does Bacula parse volume
> files for this? If the latter, has anyone done any sc
On Thu, Mar 26, 2009 at 12:40 PM, Foo wrote:
> Hi,
>
> I'm looking to mod query option 12 to list not just path/filename but size
> too, possibly other attributes like permissions, datestamps etc.
>
> Is this info kept in the catalog somewhere or does Bacula parse volume
> files for this? If the l
