>>>>> On Fri, 21 May 2021 21:21:43 -0400, Phil Stracchino said: > > On 5/21/21 5:13 PM, Phil Stracchino wrote: > > On 5/21/21 12:26 PM, Phil Stracchino wrote: > >> > >> What is the maximum possible size of File.LStat? That is another good > >> candidate to become a VARBINARY. > > > > > > The largest File.LStat value I have is 71 characters. > > > > +---------------+--------------+ > > | length(LStat) | count(LStat) | > > +---------------+--------------+ > > | 71 | 118 | > > | 70 | 2707 | > > | 69 | 5307 | > > | 68 | 66928 | > > | 67 | 74186 | > > | 66 | 396988 | > > | 65 | 775913 | > > | 64 | 1761165 | > > | 63 | 6648470 | > > | 62 | 1489408 | > > | 61 | 14953604 | > > | 60 | 3746386 | > > | 59 | 11357239 | > > | 58 | 16665912 | > > | 57 | 13653005 | > > | 56 | 12194937 | > > | 55 | 5050784 | > > | 54 | 702068 | > > | 53 | 134690 | > > | 52 | 27701 | > > | 51 | 17234 | > > | 50 | 770 | > > | 49 | 172 | > > +---------------+--------------+ > > > > > > I'm going to say VARBINARY(96) seems pretty safe here. > > > Actually upon consideration of the shape of the curve I went with > VARBINARY(80). I'll be surprised if I ever see an LStat with length 75.
I have some with length 76. But does it make any difference? I would expect the data storage size to be the same for any VARBINARY below something like 255. > What is Job.PriorJob used for? I have 486 rows currently in Job; in 480 > of them, including the 68 rows in which PriorJobId is non-zero, PriorJob > is NULL, while in the remaining six rows it is an empty string. Is it > even used? It seems to be new in version 11 and contains the Job.Job of the original Job in a Migration or Copy job. It is returned by the function BDB::bdb_find_job_start_time in src/cats/sql_find.c, where there is also a comment about it. __Martin _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
