Thread: PostgreSQL 8 on Win2003 AD server

PostgreSQL 8 on Win2003 AD server

From
Robert Fitzpatrick
Date:
I guess this is not possible? The installer cannot find the postgres
user, which is in the Active Directory. It is a Win 2003 Ent server used
here for testing things. Can someone point me to the docs for
requirements of the PostreSQL install on Windows?

--
Robert


Re: PostgreSQL 8 on Win2003 AD server

From
Robert Fitzpatrick
Date:
On Fri, 2004-09-24 at 08:47, Konstantin Danilov wrote:
> Robert,
>
> I guess you shoul have this but since you've asked... see the attached file
>
> Konstantin

So, from what I see, it should run under Windows 2003. I have Active
Directory installed, does it matter? If I create the user 'postgres' it
complains that it cannot find it. If I remove it and tell the installer
to create, it says it cannot create it. Any thoughts?

--
Robert


Re: PostgreSQL 8 on Win2003 AD server

From
"Magnus Hagander"
Date:
There is a known issue with installations on Domain Controllers. See
pgfoundry tracker item at
http://pgfoundry.org/tracker/index.php?func=detail&aid=1000096&group_id=
1000007&atid=126.

You can get through part of it by specifying DOMAIN\username, but there
may be further issues down the road from there.

If this doesn't work, you can install it *without* installing as a
service. Then create the account and register it manually using "pg_ctl
register". The issue is only in the installer, not in postgresql itself.

//Magnus

> -----Original Message-----
> From: Robert Fitzpatrick [mailto:robert@webtent.com]
> Sent: Friday, September 24, 2004 2:08 PM
> To: PostgreSQL
> Subject: [GENERAL] PostgreSQL 8 on Win2003 AD server
>
> I guess this is not possible? The installer cannot find the
> postgres user, which is in the Active Directory. It is a Win
> 2003 Ent server used here for testing things. Can someone
> point me to the docs for requirements of the PostreSQL
> install on Windows?
>
> --
> Robert
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index
> scan if your
>       joining column's datatypes do not match
>
>