CREATE EXTENSION causes script to fail if the extension already exists
Bug #1357364 reported by
Chris Sharp
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Fix Released
|
Undecided
|
Unassigned | ||
| 2.6 |
Fix Released
|
Undecided
|
Unassigned | ||
| 2.7 |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
In certain circumstances, sites may already have the "intarray" PostgreSQL extension installed, in which case, the 2.5.3-2.6.0 upgrade script should make allowances. My proposed solution is to only create the extension if it doesn't already exist:
| Changed in evergreen: | |
| milestone: | 2.6.3 → 2.6.4 |
Revision history for this message
| Ben Shum (bshum) wrote | #1 |
| Changed in evergreen: | |
| assignee: | Chris Sharp (chrissharp123) → nobody |
| milestone: | 2.6.4 → none |
| status: | New → Fix Committed |
| Changed in evergreen: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Seems reasonable to me. Picked to master and rel_2_6 for smoother upgrading.