Bug 1480624
Summary: | pg_upgrade from rh-postgresql95 fails against el7 postgresql (9.2) | ||
---|---|---|---|
Product: | Red Hat Software Collections | Reporter: | Simone Tiraboschi <stirabos> |
Component: | postgresql | Assignee: | Pavel Raiskup <praiskup> |
Status: | CLOSED NOTABUG | QA Contact: | qe-baseos-daemons |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rh-postgresql95 | CC: | databases-maint, didi, hhorak, pkubat, praiskup |
Target Milestone: | --- | ||
Target Release: | 3.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-14 10:44:29 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: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1459134 |
Description
Simone Tiraboschi
2017-08-11 14:11:22 UTC
(In reply to Simone Tiraboschi from comment #0) > The problem is that now, due to the back-porting of that change at F17 time, > pc_ctl on postgresql 9.2 shipped with el7 expects unix_socket_directories as > it's 9.3 and so it fails when run by pg_upgrade (which ignores the back-port > of the 9.3 parameter at F17 time). That's known problem; but since RHEL7 PostgreSQL 9.2 behaves differently from upstream postgresql, pg_upgrade from rhscl doesn't know whether it is performing upgrade *from* data generated by upstream postgresql server or *from* datadir generated by RHEL7 "downstream patched" server. That's why there's (temporary, for RHEL7 time-being) environment variable REDHAT_PGUPGRADE_FROM_RHEL. Set that variable to '1' and pg_upgrade should behave correctly (ie. it should use unix_socket_directories even for 9.2 server). Other option (and it is preferred!) is to (a) backup first and (b) use the 'postgresql-setup --upgrade' command wrapper (instead of using pg_upgrade directly). This way you save a lot of headaches with permissions, enabling collections, environment variables, etc. |