Bug 149552
Summary: | ResultSet.getInt alters numbers >= 2^24 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Nathan Bronson <ngb> |
Component: | postgresql | Assignee: | Tom Lane <tgl> |
Status: | CLOSED ERRATA | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | hhorak |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-02-24 01:19:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nathan Bronson
2005-02-23 22:23:40 UTC
Since we're already shipping 7.3.9 as a security erratum for RHEL3, shouldn't I just close this report as RESOLVED ERRATA? AFAIK there isn't any place to document historical bugs. Or were you just interested in creating a bugzilla entry for it? Yes, I was just trying to create a bugzilla entry, as it would have saved me a day of work. There may be others out there who haven't upgraded to the latest version yet or who are trying to balance the risk of an upgrade against the risk of not applying the errata. Fair enough, though we seldom try to make bugzilla entries for every single upstream patch included in an update ... |