Horton

Thread

  1. documentation udpates to pgupgrade.html

    Massa, Harald Armin <chef@ghum.de> — 2010-09-26T09:42:11Z

    Hello,

just doing an upgrade form PostgreSQL 8.4.4 on Windows 2007 64bit to
PostgreSQL 9.0 64bit on the same system.

I am working along
http://developer.postgresql.org/pgdocs/postgres/pgupgrade.html

There is written:

NET STOP postgresql-8.4
NET STOP postgresql-9.0
or

NET STOP pgsql-8.3  (PostgreSQL 8.3 and older used a different service name)

which should be extended by

net stop postgresql-x64-9.0

for Windows 64 bit.

-----------------

It would also be helpfull, if there was a reamrk that pg_upgrade will
try to write to the current directory - as "runas /user:postgres
cmd.exe" usually starts within c:\windows\system; so a cd %TEMP% after
runas would be valuable

-----------------



-- 
GHUM GmbH
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607

Amtsgericht Stuttgart, HRB 734971
-
persuadere.
et programmare

  2. Re: documentation udpates to pgupgrade.html

    Bruce Momjian <bruce@momjian.us> — 2010-09-28T18:43:40Z

    Massa, Harald Armin wrote:
> Hello,
> 
> just doing an upgrade form PostgreSQL 8.4.4 on Windows 2007 64bit to
> PostgreSQL 9.0 64bit on the same system.
> 
> I am working along
> http://developer.postgresql.org/pgdocs/postgres/pgupgrade.html
> 
> There is written:
> 
> NET STOP postgresql-8.4
> NET STOP postgresql-9.0
> or
> 
> NET STOP pgsql-8.3  (PostgreSQL 8.3 and older used a different service name)
> 
> which should be extended by
> 
> net stop postgresql-x64-9.0
> 
> for Windows 64 bit.
> 

Interesting.  What I have added to HEAD and 9.0 docs is the attached
patch that explains the proper service name should be used.  I don't
think I want to mention 64-bit explicitly, and in fact this section is
part of an 'e.g.' block, meaning they are just examples.  If I get more
64-bit reports I can add an example for that too.

> -----------------
> 
> It would also be helpfull, if there was a reamrk that pg_upgrade will
> try to write to the current directory - as "runas /user:postgres
> cmd.exe" usually starts within c:\windows\system; so a cd %TEMP% after
> runas would be valuable

Agreed.  Second patch attached that mentions this.

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

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

  3. Re: documentation udpates to pgupgrade.html

    Massa, Harald Armin <chef@ghum.de> — 2010-09-28T20:02:39Z

    Bruce,

>
> > NET STOP postgresql-8.4
> > NET STOP postgresql-9.0
>


> > which should be extended by
> >
> > net stop postgresql-x64-9.0
> >
> > for Windows 64 bit.
> >
>
> Interesting.  What I have added to HEAD and 9.0 docs is the attached
> patch that explains the proper service name should be used.  I don't
> think I want to mention 64-bit explicitly, and in fact this section is
> part of an 'e.g.' block, meaning they are just examples.


yes, they are only examples ... just saying that with one additional example
you could have all the fitting PostgreSQLs on Windows covered  :) ...

especially as learning about the correct service name is quite a nuisance
(it gets named magically in a sensible fassion via the one click installer;
it at least requires bringing up the service control panel and search for
sth looking like PostgreSQL)

Harald

-- 
GHUM GmbH
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607

Amtsgericht Stuttgart, HRB 734971
-
persuadere.
et programmare

  4. Re: documentation udpates to pgupgrade.html

    Bruce Momjian <bruce@momjian.us> — 2010-09-28T21:39:52Z

    Massa, Harald Armin wrote:
> Bruce,
> 
> >
> > > NET STOP postgresql-8.4
> > > NET STOP postgresql-9.0
> >
> 
> 
> > > which should be extended by
> > >
> > > net stop postgresql-x64-9.0
> > >
> > > for Windows 64 bit.
> > >
> >
> > Interesting.  What I have added to HEAD and 9.0 docs is the attached
> > patch that explains the proper service name should be used.  I don't
> > think I want to mention 64-bit explicitly, and in fact this section is
> > part of an 'e.g.' block, meaning they are just examples.
> 
> 
> yes, they are only examples ... just saying that with one additional example
> you could have all the fitting PostgreSQLs on Windows covered  :) ...
> 
> especially as learning about the correct service name is quite a nuisance
> (it gets named magically in a sensible fassion via the one click installer;
> it at least requires bringing up the service control panel and search for
> sth looking like PostgreSQL)

Can we document an easy way to find the service names?

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

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