PG crashstorage ought to do its own truncation

RESOLVED FIXED in 105

Status

Socorro
Backend
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: lars, Assigned: lars)

Tracking

unspecified
x86_64
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

4 years ago
the processor has always truncated processed crash values to fit the columns in PG's 'reports' table.  That has meant that all storage system have had their fields limited by the definition of that PG table.  

Beginning with the Processor2015, the processor will no longer truncate the fields for the convenience of PG.  That means that PG must to it's own field truncation.  

Modifiy the PG crashstorage class to enforce field lengths for its own columns, without changing the processed crash for everyone else.

Comment 1

4 years ago
Commit pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/16eb8eadac19fafad2bcbfba87cc26ef976c03eb
Merge pull request #2406 from twobraids/pg_trunc

Fixes Bug 1074245 - make pg crashstore do it's own truncation
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED

Updated

4 years ago
Target Milestone: --- → 105
You need to log in before you can comment on or make changes to this bug.