Re: Upgrade 7.4.1 to 7.4.3 not working

From: mike g <mike(at)thegodshalls(dot)com>
To: Mark Lubratt <mark(dot)lubratt(at)indeq(dot)com>
Cc: pgsql-cygwin(at)postgresql(dot)org
Subject: Re: Upgrade 7.4.1 to 7.4.3 not working
Date: 2004-07-05 05:42:02
Message-ID: 1089006122.12564.27.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-cygwin

My directory permissions for /var/log are 776 and the owner permission
is my NT domain\username with the group mkgroup-(undefined I believe).

Did you issue initdb -D /var/postgresql/data before trying to start the
postmaster?

On Fri, 2004-07-02 at 20:18, Mark Lubratt wrote:
> On Jun 30, 2004, at 10:44 PM, mike g wrote:
>
> > Can you read cygserver.log?
> >
>
> Yes.
>
> > Did the cygserver service start successfully anyway? That normally
> > runs
> > under a local system account rather than the account you installed it
> > under. If it is not running the postmaster will not start.
> >
>
> Yes, it started.
>
>
> > Files can have different permissions than the directories themselves.
> > Did you check those? By chance did you install cygserver under a
> > different user account then the one you are trying to run the configure
> > script in?
> >
>
> The cygserver.log permissions are 644 and the owner/group is
> SYSTEM/root. The directory permissions are 777 and the owner
> permission is postgres/Users.
>
> I installed everything using the same account.
>
> > Did you also upgrade the cygwin dll from 1.5.9 to 1.5.10 / install
> > using
> > the latest setup.exe from www.cygwin.com and not a previous setup.exe
> > from the 7.4.1 install?
> >
>
> I did an upgrade, then I tried a fresh install. Neither worked.
>
> Regards,
> Mark
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend

In response to

Browse pgsql-cygwin by date

  From Date Subject
Next Message cron 2004-07-05 07:51:21 Problem with NTFS (win2000)
Previous Message mike g 2004-07-05 05:23:27 Re: initdb fails with invalid argument to shmat