Re: Problem with pg_upgrade 9.2 on Windows - Mailing list pgsql-admin

From Bruce Momjian
Subject Re: Problem with pg_upgrade 9.2 on Windows
Date
Msg-id 20120914005926.GB28254@momjian.us
Whole thread Raw
In response to Re: Problem with pg_upgrade 9.2 on Windows  (Christian Ullrich <chris@chrullrich.net>)
List pgsql-admin
On Thu, Sep 13, 2012 at 11:36:56PM +0200, Christian Ullrich wrote:
> * Bruce Momjian wrote:
>
> >On Thu, Sep 13, 2012 at 02:15:00PM +0200, Christian Ullrich wrote:
>
> >>c:\Daten>path
> >>PATH=c:\windows;c:\windows\system32;c:\Program Files\PostgreSQL\9.2\bin
> >>
> >>c:\Daten>pg_upgrade --old-bindir="c:\Program Files\PostgreSQL\9.1\bin"
> >>--new-bindir="c:\Program Files\PostgreSQL\9.2\bin"
> >>--old-datadir="c:\Daten\db\pgsql"
> >>--new-datadir=c:\Daten\db\pgsql-9.2\data --old-port=5432
> >>--new-port=5433 --user=postgres --verbose --check
> >
> >So I assume this is an upgrade from 9.1 to 9.2, based on the prompts,
> >right?
>
> 9.1.5 to 9.2.0.
>
> And, as all to usual, I find myself apologizing for wasting
> everyone's time after finding my problem just after asking for help.
> It was my fault; while I'm too embarrassed to go into the details,
> let's just say there was an environmental discrepancy I had caused.

OK.  I would love to know how a misconfiguration would remove a text
string from a command, but hey, as long as it is now working for you.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +


pgsql-admin by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: what is maximum allowed value of autovacuum_freeze_max_age
Next
From: Rural Hunter
Date:
Subject: pg_upgrade from 9.1.3 to 9.2 failed