Re: PostgreSQL for NT

Hi,

Sorry for the delay. I have to work too.
Ok, thanks the first problem is solved, the second one came up.

I now can run the postmaster:
C:\>ipc-daemon &
C:\>postmaster -i &
DEBUG: Data Base System is starting up at Thu Nov 23 22:19:40 2000
DEBUG: Data Base System was interrupted being in production at Tue Nov 21 21:55:37 2000
DEBUG: Data Base System is in production state at Thu Nov 23 22:19:40 2000

But when I start the psql client on the same machine, I get:

C:\Postgres>psql -h localhost -d template1
psql: Missing or erroneous pg_hba.conf file, see postmaster log for details

The postmaster windows looks like:

C:\>postmaster -i &
DEBUG: Data Base System is starting up at Thu Nov 23 22:19:40 2000
DEBUG: Data Base System was interrupted being in production at Tue Nov 21 21:55:37 2000
DEBUG: Data Base System is in production state at Thu Nov 23 22:19:40 2000
process_hba_record: invalid syntax in pg_hba.conf file
Missing or erroneous pg_hba.conf file, see postmaster log for details

I thought (perhaps a mistake) the DOS-UNIX conversion is bugging me. So I migrated pg_hba.conf to
a UNIX style text file.
The result was:
C:\Postgres>psql -h localhost -d template1
NOTICE: mdopen: couldn't open c:/cygwin/usr/local/pgsql/data/pg_log: No such file or directory
NOTICE: mdopen: couldn't open c:/cygwin/usr/local/pgsql/data/pg_variable: No such file or directory
NOTICE: mdopen: couldn't open c:/cygwin/usr/local/pgsql/data/pg_log: No such file or directory
psql: FATAL 1: cannot open relation pg_log

All line in pg_hba.conf are commented except this one (which looks fine to me):
host all 127.0.0.1 255.255.255.255 trust

Any help on this one?

TIA

Willem

----- Original Message -----
From: "Jason Tishler" <Jason(dot)Tishler(at)dothill(dot)com>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Cc: "W. van den Akker" <wvdakker(at)wilsoft(dot)nl>; <pgsql-ports(at)postgresql(dot)org>
Sent: Sunday, November 19, 2000 3:53 AM
Subject: Re: [PORTS] PostgreSQL for NT

> Peter,
>
> On Sun, Nov 19, 2000 at 01:14:10AM +0100, Peter Eisentraut wrote:
> > W. van den Akker writes:
> >
> > > FindExec: could not find a postgres to execute...
> > > FATAL 1: postgres: could not locate executable, bailing out...
> > > FATAL 1: postgres: could not locate executable, bailing out...
> > >
> > > If I run postgres.exe from the bash shell then I have no problems.
> >
> > The reason for this is that the program does a shell-like path walk to
> > find itself. If you are not running a Unix-like shell then you don't have
> > a PATH variable in the environment (or at least you have one with
> > semicolons as separators). Using absolute file names might work.
>
> If postmaster.exe is a copy of postgres.exe (instead of a symlink) and I
> have the following defined in my environment:
>
> Path=C:\WINNT\system32;C:\Cygwin\1.1.4\bin;C:\Cygwin\1.1.4\usr\local\pgsql\bin
> PGDATA=/usr/local/pgsql/data
>
> then postmaster -i startups directly from cmd without any problems.
>
> Cygwin automatically converts certain environment variables between
> Win32 and POSIX -- PATH is one of them. So, if postgres.exe is using
> PATH (which seems to be implied above) when it tries to "find itself,"
> then the "shell-like path walk" should work as expected.
>
> Jason
>
> --
> Jason Tishler
> Director, Software Engineering Phone: +1 (732) 264-8770 x235
> Dot Hill Systems Corporation Fax: +1 (732) 264-8798
> 82 Bethany Road, Suite 7 Email: Jason(dot)Tishler(at)dothill(dot)com
> Hazlet, NJ 07730 USA WWW: http://www.dothill.com
>
>