| Summary: | User not prompted to upgrade Postgres after upgrade from F19 to F20 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Rob Sharp <rob> |
| Component: | postgresql | Assignee: | Pavel Raiskup <praiskup> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | devrim, hhorak, jmlich, jstanek, praiskup, tgl, wwoods |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-13 17:55:01 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Rob Sharp
2013-10-12 21:51:23 UTC
Thanks for this report, Rob. I expect that everything is OK after database upgrade, yes? I don't think there can be done more that just in fedup add some "note" that user should (after full reboot) do 'postgresql-setup upgrade'. As I'm not aware of any "plug-in" capability of fedup, this would have to be done directly in package fedup. Really, this would be more like a "content" adjusting for some versions of Fedora which just duplicates the work, because the way you were instructed to run 'postgresql-setup upgrade' is IMO straight forward and IMO very valid. For me this is NOTABUG. But feel free to reopen if you see that we may do something in PostgreSQL or reopen against fedup, if you feel there should be some note. Pavel Hi Pavel, Yes - everything was fine after the upgrade. I thought I'd bring this to your attention but, if you believe everything is as it should be, I'm fine with that! - Rob > I thought I'd bring this to your attention but, [...]
Thanks for bringing it this way once again - it will be burned in bugzilla
forever so anybody may start from this point in future.
This issue is nothing which does not hurt us, but the database upgrade process
is not very easy for full automation. And "in-place" upgrade of Fedora is
definitely hard task right because problems like this one.
I am adding maintainer of 'fedup' to CC, maybe he could point us some expected
way for Feodra, Will? Is there a way (not considering %post* scriplets, it
would be IMO non-maintainable) how to notify user that some action is required
after Fedora upgrade?
> This issue is nothing which does not hurt us
s/is nothing/is not a problem/ :)
(In reply to Pavel Raiskup from comment #3) > I am adding maintainer of 'fedup' to CC, maybe he could point us some > expected > way for Feodra, Will? Is there a way (not considering %post* scriplets, it > would be IMO non-maintainable) how to notify user that some action is > required > after Fedora upgrade? Anything that can be done *automatically* for *all users* should be done in a package %post/%posttrans script. Anything that requires user interaction to decide what to do.. should be handled by some other pre- or post-upgrade service. (No such service exists yet, though.) FWIW, our historical position on this has been that an *automatic* major-version upgrade would be a seriously bad idea. Postgres major version updates usually involve some amount of client-visible incompatibilities, which a user might not want to deal with right away during an OS upgrade. In the past, the way was open to install a self-compiled previous-version server and keep using that until you were ready for the PG server upgrade. If we automatically upgrade the database during the OS upgrade then such a user is out of luck. There's no upstream support for reversing a database storage upgrade, and I doubt it'd work reliably. |