Librarian does not check upper limit on filesize

Bug #499751 reported by Michael Nelson
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Stuart Bishop

Bug Description

We currently store the file size of Librarian files in the database using a normal PostgreSQL integer. This does not support files larger than 2GB. We should switch this column to bigint to support DVD images or huge source packages, such as discussed in where a person was uploading a 3gb source package and was not receiving any upload error even though the file uploaded successfully.

The following log shows the exception while processing the upload:

and the actual traceback is:

which shows that "DataError: integer out of range" is raised because we're using PostgreSQL's (signed) 4byte integer to store the file size (max. 2147483648 bytes).

description: updated
affects: soyuz → launchpad-foundations
Stuart Bishop (stub)
description: updated
Changed in launchpad-foundations:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Stuart Bishop (stub)
milestone: none → 10.01
Stuart Bishop (stub)
Changed in launchpad-foundations:
status: Confirmed → In Progress
Stuart Bishop (stub)
Changed in launchpad-foundations:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in launchpad-foundations:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.