From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | bernhard(dot)schrader(at)innogames(dot)de |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #7683: pg_upgrade missing configuration file |
Date: | 2012-11-23 22:44:21 |
Message-ID: | 20121123224421.GC22603@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Nov 20, 2012 at 11:23:13AM +0000, bernhard(dot)schrader(at)innogames(dot)de wrote:
> To point this out, postgresql 9.0 and 9.2 are not running, if 9.0 is
> running, the 9.0 tests succeed, but afaik they shouldn't running, or at
> least 9.2 shouldn't running during upgrade, but without the link to the
> config it will never start. The same for 9.0, if it is shut down and the
> link is present, it works. I assume this is a "bug" or at least a missing
> option for pg_upgrade in addition to debian. Do you confirm? Or do i
> undestand something completly wrong? I hope not, thanks in advance
Have you seen this in the pg_upgrade 9.2 manual?
If you are upgrading a pre-<productname>PostgreSQL</> 9.2 cluster
that uses a configuration-file-only directory, you must pass the
real data directory location to <application>pg_upgrade</>, and
pass the configuration directory location to the server, e.g.
<literal>-d /real-data-directory -o '-D /configuration-directory'</>.
-o, --old-options=OPTIONS old cluster options to pass to the server
-O, --new-options=OPTIONS new cluster options to pass to the server
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | maxim.boguk | 2012-11-25 23:21:23 | BUG #7703: Error with partitioning with distinct over aggregate |
Previous Message | Tom Lane | 2012-11-23 16:34:37 | Re: [GENERAL] Prepared Statement Name Truncation |