Can you tell me any consequences from this bug?  I'm testing bacula before using them in our production environment and would like to know if this is a show stopper.

Thanks,

Joe

On 4/11/06, Kern Sibbald <[EMAIL PROTECTED]> wrote:
On Monday 10 April 2006 21:33, Joe Park wrote:
> bacula ver: 1.38.6
> OS: FreeBSD 6.0
> DB: postgresql 8.1.3
> Changer/Tapedrive: Dell PowerVault 122T
>
>
> Hello,
>
> I have this error messeges repeated in system log file --
>
>
> Apr  9 03:40:47 localhost postgres[18833]: [1-1] ERROR:  column
> file.markedid does not exist
> Apr  9 06:38:20 localhost postgres[20267]: [1-1] ERROR:  column
> file.markedid does not exist
> Apr  9 10:04:23 localhost postgres[21200]: [1-1] ERROR:  column
> file.markedid does not exist
>
>
> The error coincides with bacula verify job end time.  I see that bacula db
> has file.mark column, but not file.markedid column.  Any help is
> appreciated.

This is a bug (typo in SQL).  I have just fixed it.  Thanks for reporting it.

The fix will be in 1.38.8

--
Best regards,

Kern

  (">
  /\
  V_V

Reply via email to