filename.filenameid out of range

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

filename.filenameid out of range

Marek Becka
Hi,

we are running Bacula director with the catalog in PostgreSQL for almost
4 years.  At current time  director is used for approximately 720
clients, the database size is 700GB with 534680929 records in the
relation filename and 71034586 records in the relation path.


Last week we encountered an error message during backup job:


bacula-dir JobId 704869: Fatal error: sql_create.c:814 Fill Filename
table Query failed: INSERT INTO Filename (Name) SELECT a.Name FROM
(SELECT DISTINCT Name FROM batch) as a WHERE NOT EXISTS (SELECT Name
FROM Filename WHERE Name = a.Name): ERR=ERROR: integer out of range


To keep backups running we have to change definition od type for columns
filename.filenameid and file.filenameid from integer to bigint.

I have several questions:

1. Is it safe to use bigint instead of integer?
2. Have anyone else encountered this issue?
3. Wouldn't it be reasonable to change type for filename.filenameid from
serial to bigserial in the database creation script for future versions
of Bacula?

Kind regards
Marek Becka


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
Loading...