From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | jwhiting(at)redhat(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #13646: Upgrading existing db from 9.2 to 9.4.4 not working using postgresql-setup. |
Date: | 2015-09-28 13:38:37 |
Message-ID: | 18419.1443447517@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
jwhiting(at)redhat(dot)com writes:
> The following bug has been logged on the website:
> Bug reference: 13646
> Logged by: Jeremy Whiting
> Email address: jwhiting(at)redhat(dot)com
> PostgreSQL version: 9.4.4
> Operating system: Fedora 22, Linux burtha-f22 4.1.6-200.fc22.x86_64
> Description:
> Hi,
> I have been trying to upgrade a database created using 9.2.0. Using the
> postgresql-setup version 9.4.4. This issue happens on two machines both
> running Fedora 22.
You would be better off filing this in Red Hat's bugzilla, because
postgresql-setup is Red Hat's code not the PG community's. However,
I think what you'll be told is that postgresql-setup isn't intended to
handle upgrades across more than one major Postgres version. It certainly
wouldn't have been able to when I worked there, because it's only packaged
with a postmaster executable for the immediately preceding major Postgres
version.
Perhaps you can persuade the guys to redesign the packaging to handle
such cases, but here is not where to ask for it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-09-28 16:28:03 | Re: BUG #13638: Exception texts from plperl has bad encoding |
Previous Message | beni | 2015-09-28 09:08:04 | BUG #13647: Error after upgrade 9.3->9.4: materialized view `foo` has not been populated |