Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 6768B63392D for ; Fri, 11 Jun 2010 10:51:22 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 56083-06 for ; Fri, 11 Jun 2010 13:51:10 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ww0-f46.google.com (mail-ww0-f46.google.com [74.125.82.46]) by mail.postgresql.org (Postfix) with ESMTP id 3D34F632C3C for ; Fri, 11 Jun 2010 10:51:10 -0300 (ADT) Received: by wwb18 with SMTP id 18so746265wwb.19 for ; Fri, 11 Jun 2010 06:51:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=i5K1XmeKbPnqi29F98wSt9g02n2rRMhzipq9t7ONj1c=; b=X3RWMfQq9DWFbhUPsGLkGMSCdkvdiEGqKfyVd2SuDwGzFeyJQ3Sj47BFk6lnBJ5BsZ AyqlK4SWU9fCS02CuLkyKZyjMClZlRbzauWHnP9cVcQjEumC63Z65b2KEyDH/3e1f7oY HrkPHqQuT6LPWoiR94rxuHyh5kfzrH2L2iAaU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=ge9FVS0ZrLLCfZoUik5J+NQMWuFMCph9/BqAoJ2ewelFj4M8SiPemVmh9rOoNNUhaQ rSJD6+c+qSPJYqGMQQ5KUnJA0hvpcJk2Ya2ile1/zOznBWTdpxxcWuHvQ419wbGatvS4 mwA9nLq3jfU/WJqJgm8QR7SUNykX4FhvA9iLM= Received: by 10.227.134.197 with SMTP id k5mr1921009wbt.95.1276264265827; Fri, 11 Jun 2010 06:51:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.188.209 with HTTP; Fri, 11 Jun 2010 06:50:45 -0700 (PDT) From: Thom Brown Date: Fri, 11 Jun 2010 14:50:45 +0100 Message-ID: Subject: pg_upgrade invalid option To: pgsql-docs Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.5 tagged_above=-5 required=5 tests=BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201006/16 X-Sequence-Number: 5584 I've tried following the instructions on this page: http://www.postgresql.org/files/documentation/books/aw_pgsql/node267.html This mentions a -f option but my version of pg_upgrade doesn't appear to support this: /usr/lib64/postgresql-9.0/bin/pg_upgrade: invalid option -- 'f' The only options available are: Options: -b, --old-bindir=old_bindir old cluster executable directory -B, --new-bindir=new_bindir new cluster executable directory -c, --check check clusters only, don't change any data -d, --old-datadir=old_datadir old cluster data directory -D, --new-datadir=new_datadir new cluster data directory -g, --debug enable debugging -G, --debugfile=debug_filename output debugging activity to file -k, --link link instead of copying files to new cluster -l, --logfile=log_filename log session activity to file -p, --old-port=old_portnum old cluster port number (default 5432) -P, --new-port=new_portnum new cluster port number (default 5432) -u, --user=username clusters superuser (default "postgres") -v, --verbose enable verbose output -V, --version display version information, then exit -h, --help show this help, then exit Are those instructions for an older version? Thanks Thom