| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | William <whairs01(at)hotmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: FW: Unable to install PostgreSQL on Windows Server 2003 SP2 |
| Date: | 2010-02-24 21:33:57 |
| Message-ID: | 937d27e11002241333g54c20191j2b5f4d74e34252ea@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 24, 2010 at 8:15 PM, Richard Huxton <dev(at)archonet(dot)com> wrote:
> If that all works, re-run the installer and you should be able to re-install
> the adminpack etc. over the top of your now working installation.
That won't work. If the installer finds the existing data directory
(which it will), it won't try to run initdb or modify it in any way.
It'll just check the catalog version and datetime format are
compatible.
You'd have to run the adminpack SQL script manually.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
PG East Conference: http://www.enterprisedb.com/community/nav-pg-east-2010.do
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2010-02-24 21:35:34 | Probably badly timed suggestion: pl/perl calling style same as C style |
| Previous Message | Josh Berkus | 2010-02-24 21:30:50 | Re: pg_stop_backup does not complete |