Closed
Bug 700839
Opened 14 years ago
Closed 14 years ago
Update PostgreSQL servers to version 9.0.6
Categories
(Socorro :: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
2.4.1
People
(Reporter: jberkus, Assigned: mpressman)
Details
(Whiteboard: [qa-])
While PostgreSQL 9.0.5 does not have any critical fixes in it which affect our application, it's a good idea to keep up with the latest patches. As such, I'd like to schedule an update of our production servers as soon as convenient.
| Reporter | ||
Comment 1•14 years ago
|
||
Postponing this, because it looks like 9.0.6 will come out on Dec. 5th or 6th.
Summary: Update PostgreSQL servers to version 9.0.5 → Update PostgreSQL servers to version 9.0.6
Target Milestone: 2.3.4 → 2.4.1
| Reporter | ||
Comment 2•14 years ago
|
||
Jason,
9.0.6 is available as of last week. The release contains a bug fix for an issue which could cause production to fail to fail over properly in the event of an emergency failover, so it's important to get it installed soon.
When can we reasonably schedule an update? This requires around 5min of downtime.
| Reporter | ||
Comment 3•14 years ago
|
||
assigned to mpressman by request.
"yum update postgresql90" was tested on stage, and worked with no further steps required.
Normally we look on postgres updates as a time to test failover as well, failing over to master02 and back to master01 to make sure that's still working. However, given IT resources after last week's outages, this might be a bad idea in case there *are* issues.
Assignee: josh → mpressman
Comment 4•14 years ago
|
||
As this will cause a Socorro production outage for ~5 min we plan to do this later in the day on Thursday Dec 15 @ 6PM PST.
@laura: Does this date and time work for you?
Updated•14 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
| Assignee | ||
Comment 5•14 years ago
|
||
tp-socorro01-master01 and tp-socorro01-master02 have been upgraded to postgresql 9.0.6. The upgrade went smooth with the exception of the processors which did not automatically reconnect and needed to be manually restarted
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•14 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•