Old is 8.4, new is 9.2. I am not supplying an but the minimum options and -=
-check succeeds. My pg_ctl fails when run by hand with -w (although the dat=
abase does start) so I know that's the issue.
On Feb 14, 2013, at 9:50 PM, Ian Lawrence Barwick <barwick@gmail.com> wrote:=
> 2013/2/15 Ian Harding <harding.ian@gmail.com>
>> When I run pg_upgrade, it tries to start the old cluster with the -w flag=
, which waits a while and declares failure, even though it starts the server=
. If I start/stop without -w everything is great. =20
>>=20
>> Can I tell pg_upgrade not to use that flag, or is there a reason it is no=
t working that I should look into?
>>=20
>> version =
=20
>> -------------------------------------------------------------------------=
-----------------------------
>> PostgreSQL 8.4.8 on x86_64-pc-linux-gnu, compiled by GCC gcc-4.4.real (D=
ebian 4.4.5-8) 4.4.5, 64-bit
>>=20
>=20
>=20
> Which PostgreSQL version is the old cluster, and which version is the new c=
luster? What options are you supplying to pg_upgrade, and what output are yo=
u getting?=20
>=20
> Ian Barwick
