Re: Runtime Problems

Hello All

I am quite new to pgsql and the Win32 port. I have just tried Vishal's new
guide to building
and I am having what looks like a path problem when I try to initialise a
database. I am using
Windows 2000. Everything builds and installs OK and I have copied the files
in the msys\1.0\local\pgsql
to my c:\pgsql folder as per the instructions. I have added C:\pgsql\bin and
c:\pgsql\lib to my path
as instructed. When I try to run initdb I get the following error

initdb -D c:\pgsql\data -W --lc-collate=C
Bad command or file name
fgets failure: No error
Bad command or file name
fgets failure: No error
The program "postgres" is needed by initdb but was not found in
the directory "C:/msys/1.0/local/pgsql/bin". Check your installation

I would appreciate any clues here as this has me stumped. I don't understand
why is should even be looking in the msys directory.

Regards

Richard
_______________________________________
Richard Luckhurst
Manager / Engineer
Sound Advice / BSP Internet Services
P.O. Box 104
Narrabri NSW 2390
Ph / Fax 02 6792 6060
http://www.bsp.aunz.com

Richard Luckhurst said:
> Hello All
>
> I am quite new to pgsql and the Win32 port. I have just tried Vishal's
> new guide to building
> and I am having what looks like a path problem when I try to initialise
> a database. I am using
> Windows 2000. Everything builds and installs OK and I have copied the
> files in the msys\1.0\local\pgsql
> to my c:\pgsql folder as per the instructions. I have added
> C:\pgsql\bin and c:\pgsql\lib to my path
> as instructed. When I try to run initdb I get the following error
>
> initdb -D c:\pgsql\data -W --lc-collate=C
> Bad command or file name
> fgets failure: No error
> Bad command or file name
> fgets failure: No error
> The program "postgres" is needed by initdb but was not found in
> the directory "C:/msys/1.0/local/pgsql/bin". Check your installation
>
> I would appreciate any clues here as this has me stumped. I don't
> understand why is should even be looking in the msys directory.
>

I haven't had time to read the document referred to, but if it currently
recommends that you run from anywhere but the installed path then I
disagree with it. When we get relocatable installs, which Bruce is working
on, you will be able to move the whole installation around to your heart's
content.

Have you checked that there is still in fact a
C:/msys/1.0/local/pgsql/bin/postgres.exe? Could it be a permissions
problem?

cheers

andrew

Hi Andrew

> Have you checked that there is still in fact a
> C:/msys/1.0/local/pgsql/bin/postgres.exe? Could it be a permissions
> problem?

Yes there is as I left the entire default installation in place.
I have checked the permissions and everything in the bin directory is
group and world readable and executable.

regards

Richard

I said:
> Richard Luckhurst said:
>> Hello All
>>
>> I am quite new to pgsql and the Win32 port. I have just tried Vishal's
>> new guide to building
>> and I am having what looks like a path problem when I try to
>> initialise a database. I am using
>> Windows 2000. Everything builds and installs OK and I have copied the
>> files in the msys\1.0\local\pgsql
>> to my c:\pgsql folder as per the instructions. I have added
>> C:\pgsql\bin and c:\pgsql\lib to my path
>> as instructed. When I try to run initdb I get the following error
>>
>> initdb -D c:\pgsql\data -W --lc-collate=C

The clue is actually in these following 4 lines

>> Bad command or file name
>> fgets failure: No error
>> Bad command or file name
>> fgets failure: No error

For some reason, initdb has found postgres.exe in 2 locations but in both
cases has been unable to execute it, and consequently unable to read in
the version string.

That's a bit strange - I have no explanation for it right now.

The relevant code has just been refactored by Bruce as part of the
relocation stuff.

For now, I still recommend running from the installed path.

cheers

andrew

>> The program "postgres" is needed by initdb but was not found in
>> the directory "C:/msys/1.0/local/pgsql/bin". Check your installation
>>
>> I would appreciate any clues here as this has me stumped. I don't
>> understand why is should even be looking in the msys directory.
>>
>
> I haven't had time to read the document referred to, but if it
> currently recommends that you run from anywhere but the installed path
> then I disagree with it. When we get relocatable installs, which Bruce
> is working on, you will be able to move the whole installation around
> to your heart's content.
>
> Have you checked that there is still in fact a
> C:/msys/1.0/local/pgsql/bin/postgres.exe? Could it be a permissions
> problem?
>

Hi All

I have just recompiled using the latest snapshot and I am still getting
exactly the same errors. I still have the compile stuff in msys and the copy
in c:\pgsql so that explains why it is picking it up twice I guess. In any
case I still have the error I first asked about last week.

Regards

Richard

-----Original Message-----
From: pgsql-hackers-win32-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
Dunstan
Sent: Thursday, 13 May 2004 8:54 PM
To: pgsql-hackers-win32(at)postgresql(dot)org
Subject: Re: [pgsql-hackers-win32] Runtime Problems

I said:
> Richard Luckhurst said:
>> Hello All
>>
>> I am quite new to pgsql and the Win32 port. I have just tried Vishal's
>> new guide to building
>> and I am having what looks like a path problem when I try to
>> initialise a database. I am using
>> Windows 2000. Everything builds and installs OK and I have copied the
>> files in the msys\1.0\local\pgsql
>> to my c:\pgsql folder as per the instructions. I have added
>> C:\pgsql\bin and c:\pgsql\lib to my path
>> as instructed. When I try to run initdb I get the following error
>>
>> initdb -D c:\pgsql\data -W --lc-collate=C

The clue is actually in these following 4 lines

>> Bad command or file name
>> fgets failure: No error
>> Bad command or file name
>> fgets failure: No error

For some reason, initdb has found postgres.exe in 2 locations but in both
cases has been unable to execute it, and consequently unable to read in
the version string.

That's a bit strange - I have no explanation for it right now.

The relevant code has just been refactored by Bruce as part of the
relocation stuff.

For now, I still recommend running from the installed path.

cheers

andrew

>> The program "postgres" is needed by initdb but was not found in
>> the directory "C:/msys/1.0/local/pgsql/bin". Check your installation
>>
>> I would appreciate any clues here as this has me stumped. I don't
>> understand why is should even be looking in the msys directory.
>>
>
> I haven't had time to read the document referred to, but if it
> currently recommends that you run from anywhere but the installed path
> then I disagree with it. When we get relocatable installs, which Bruce
> is working on, you will be able to move the whole installation around
> to your heart's content.
>
> Have you checked that there is still in fact a
> C:/msys/1.0/local/pgsql/bin/postgres.exe? Could it be a permissions
> problem?
>

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

__________ NOD32 1.759 (20040513) Information __________

This message was checked by NOD32 antivirus system.
http://www.nod32.com

Richard Luckhurst said:
> Hi All
>
> I have just recompiled using the latest snapshot and I am still getting
> exactly the same errors. I still have the compile stuff in msys and the
> copy in c:\pgsql so that explains why it is picking it up twice I
> guess. In any case I still have the error I first asked about last
> week.

What parameters did you run configure with?

cheers

andrew

>
> Regards
>
> Richard
>
> -----Original Message-----
> From: pgsql-hackers-win32-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
> Dunstan
> Sent: Thursday, 13 May 2004 8:54 PM
> To: pgsql-hackers-win32(at)postgresql(dot)org
> Subject: Re: [pgsql-hackers-win32] Runtime Problems
>
>
> I said:
>> Richard Luckhurst said:
>>> Hello All
>>>
>>> I am quite new to pgsql and the Win32 port. I have just tried
>>> Vishal's new guide to building
>>> and I am having what looks like a path problem when I try to
>>> initialise a database. I am using
>>> Windows 2000. Everything builds and installs OK and I have copied the
>>> files in the msys\1.0\local\pgsql
>>> to my c:\pgsql folder as per the instructions. I have added
>>> C:\pgsql\bin and c:\pgsql\lib to my path
>>> as instructed. When I try to run initdb I get the following error
>>>
>>> initdb -D c:\pgsql\data -W --lc-collate=C
>
> The clue is actually in these following 4 lines
>
>>> Bad command or file name
>>> fgets failure: No error
>>> Bad command or file name
>>> fgets failure: No error
>
> For some reason, initdb has found postgres.exe in 2 locations but in
> both cases has been unable to execute it, and consequently unable to
> read in the version string.
>
> That's a bit strange - I have no explanation for it right now.
>
> The relevant code has just been refactored by Bruce as part of the
> relocation stuff.
>
> For now, I still recommend running from the installed path.
>
> cheers
>
> andrew
>
>
>>> The program "postgres" is needed by initdb but was not found in the
>>> directory "C:/msys/1.0/local/pgsql/bin". Check your installation
>>>
>>> I would appreciate any clues here as this has me stumped. I don't
>>> understand why is should even be looking in the msys directory.
>>>
>>
>> I haven't had time to read the document referred to, but if it
>> currently recommends that you run from anywhere but the installed path
>> then I disagree with it. When we get relocatable installs, which Bruce
>> is working on, you will be able to move the whole installation around
>> to your heart's content.
>>
>> Have you checked that there is still in fact a
>> C:/msys/1.0/local/pgsql/bin/postgres.exe? Could it be a permissions
>> problem?
>>
>
>

Hi Andrew

I ran configure with the --without-zlib option

Regards

Richard

-----Original Message-----
From: pgsql-hackers-win32-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
Dunstan
Sent: Sunday, 16 May 2004 8:13 PM
To: pgsql-hackers-win32(at)postgresql(dot)org
Subject: Re: [pgsql-hackers-win32] Runtime Problems

Richard Luckhurst said:
> Hi All
>
> I have just recompiled using the latest snapshot and I am still getting
> exactly the same errors. I still have the compile stuff in msys and the
> copy in c:\pgsql so that explains why it is picking it up twice I
> guess. In any case I still have the error I first asked about last
> week.

What parameters did you run configure with?

cheers

andrew

>
> Regards
>
> Richard
>
> -----Original Message-----
> From: pgsql-hackers-win32-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
> Dunstan
> Sent: Thursday, 13 May 2004 8:54 PM
> To: pgsql-hackers-win32(at)postgresql(dot)org
> Subject: Re: [pgsql-hackers-win32] Runtime Problems
>
>
> I said:
>> Richard Luckhurst said:
>>> Hello All
>>>
>>> I am quite new to pgsql and the Win32 port. I have just tried
>>> Vishal's new guide to building
>>> and I am having what looks like a path problem when I try to
>>> initialise a database. I am using
>>> Windows 2000. Everything builds and installs OK and I have copied the
>>> files in the msys\1.0\local\pgsql
>>> to my c:\pgsql folder as per the instructions. I have added
>>> C:\pgsql\bin and c:\pgsql\lib to my path
>>> as instructed. When I try to run initdb I get the following error
>>>
>>> initdb -D c:\pgsql\data -W --lc-collate=C
>
> The clue is actually in these following 4 lines
>
>>> Bad command or file name
>>> fgets failure: No error
>>> Bad command or file name
>>> fgets failure: No error
>
> For some reason, initdb has found postgres.exe in 2 locations but in
> both cases has been unable to execute it, and consequently unable to
> read in the version string.
>
> That's a bit strange - I have no explanation for it right now.
>
> The relevant code has just been refactored by Bruce as part of the
> relocation stuff.
>
> For now, I still recommend running from the installed path.
>
> cheers
>
> andrew
>
>
>>> The program "postgres" is needed by initdb but was not found in the
>>> directory "C:/msys/1.0/local/pgsql/bin". Check your installation
>>>
>>> I would appreciate any clues here as this has me stumped. I don't
>>> understand why is should even be looking in the msys directory.
>>>
>>
>> I haven't had time to read the document referred to, but if it
>> currently recommends that you run from anywhere but the installed path
>> then I disagree with it. When we get relocatable installs, which Bruce
>> is working on, you will be able to move the whole installation around
>> to your heart's content.
>>
>> Have you checked that there is still in fact a
>> C:/msys/1.0/local/pgsql/bin/postgres.exe? Could it be a permissions
>> problem?
>>
>
>

---------------------------(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

__________ NOD32 1.762 (20040516) Information __________

This message was checked by NOD32 antivirus system.
http://www.nod32.com

Richard Luckhurst wrote:

>Hi Andrew
>
>I ran configure with the --without-zlib option
>

What happens if you cd to c:\pgsql and run

bin/initdb -D c:\pgsql\data -W --lc-collate=C

?

cheers

andrew

>
>Regards
>
>Richard
>
>-----Original Message-----
>From: pgsql-hackers-win32-owner(at)postgresql(dot)org
>[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
>Dunstan
>Sent: Sunday, 16 May 2004 8:13 PM
>To: pgsql-hackers-win32(at)postgresql(dot)org
>Subject: Re: [pgsql-hackers-win32] Runtime Problems
>
>
>Richard Luckhurst said:
>
>
>>Hi All
>>
>>I have just recompiled using the latest snapshot and I am still getting
>>exactly the same errors. I still have the compile stuff in msys and the
>>copy in c:\pgsql so that explains why it is picking it up twice I
>>guess. In any case I still have the error I first asked about last
>>week.
>>
>>
>
>What parameters did you run configure with?
>
>cheers
>
>andrew
>
>
>
>
>>Regards
>>
>>Richard
>>
>>-----Original Message-----
>>From: pgsql-hackers-win32-owner(at)postgresql(dot)org
>>[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
>>Dunstan
>>Sent: Thursday, 13 May 2004 8:54 PM
>>To: pgsql-hackers-win32(at)postgresql(dot)org
>>Subject: Re: [pgsql-hackers-win32] Runtime Problems
>>
>>
>>I said:
>>
>>
>>>Richard Luckhurst said:
>>>
>>>
>>>>Hello All
>>>>
>>>>I am quite new to pgsql and the Win32 port. I have just tried
>>>>Vishal's new guide to building
>>>>and I am having what looks like a path problem when I try to
>>>>initialise a database. I am using
>>>>Windows 2000. Everything builds and installs OK and I have copied the
>>>>files in the msys\1.0\local\pgsql
>>>>to my c:\pgsql folder as per the instructions. I have added
>>>>C:\pgsql\bin and c:\pgsql\lib to my path
>>>>as instructed. When I try to run initdb I get the following error
>>>>
>>>>initdb -D c:\pgsql\data -W --lc-collate=C
>>>>
>>>>
>>The clue is actually in these following 4 lines
>>
>>
>>
>>>>Bad command or file name
>>>>fgets failure: No error
>>>>Bad command or file name
>>>>fgets failure: No error
>>>>
>>>>
>>For some reason, initdb has found postgres.exe in 2 locations but in
>>both cases has been unable to execute it, and consequently unable to
>>read in the version string.
>>
>>That's a bit strange - I have no explanation for it right now.
>>
>>The relevant code has just been refactored by Bruce as part of the
>>relocation stuff.
>>
>>For now, I still recommend running from the installed path.
>>
>>cheers
>>
>>andrew
>>
>>
>>
>>
>>>>The program "postgres" is needed by initdb but was not found in the
>>>>directory "C:/msys/1.0/local/pgsql/bin". Check your installation
>>>>
>>>>I would appreciate any clues here as this has me stumped. I don't
>>>>understand why is should even be looking in the msys directory.
>>>>
>>>>
>>>>
>>>I haven't had time to read the document referred to, but if it
>>>currently recommends that you run from anywhere but the installed path
>>>then I disagree with it. When we get relocatable installs, which Bruce
>>>is working on, you will be able to move the whole installation around
>>>to your heart's content.
>>>
>>>Have you checked that there is still in fact a
>>>C:/msys/1.0/local/pgsql/bin/postgres.exe? Could it be a permissions
>>>problem?
>>>
>>>
>>>
>>
>>
>
>
>
>
>---------------------------(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
>
>
>__________ NOD32 1.762 (20040516) Information __________
>
>This message was checked by NOD32 antivirus system.
>http://www.nod32.com
>
>
>
>

Richard Luckhurst wrote:
> Hi Andrew
>
> I ran configure with the --without-zlib option

Should we default to this on Win32?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

Hi Andrew

if I try to just run bin/initdb in the pgsql directory I get the normal
error
that bin is not an executable. If I try the full path c:\pgsql\bin\initdb I
get the same old error.

Regards

Richard

-----Original Message-----
From: Andrew Dunstan [mailto:andrew(at)dunslane(dot)net]
Sent: Monday, 17 May 2004 9:42 AM
To: Richard Luckhurst
Cc: PGSQL Hackers
Subject: Re: [pgsql-hackers-win32] Runtime Problems

Richard Luckhurst wrote:

>Hi Andrew
>
>I ran configure with the --without-zlib option
>

What happens if you cd to c:\pgsql and run

bin/initdb -D c:\pgsql\data -W --lc-collate=C

?

cheers

andrew

>
>Regards
>
>Richard
>
>-----Original Message-----
>From: pgsql-hackers-win32-owner(at)postgresql(dot)org
>[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
>Dunstan
>Sent: Sunday, 16 May 2004 8:13 PM
>To: pgsql-hackers-win32(at)postgresql(dot)org
>Subject: Re: [pgsql-hackers-win32] Runtime Problems
>
>
>Richard Luckhurst said:
>
>
>>Hi All
>>
>>I have just recompiled using the latest snapshot and I am still getting
>>exactly the same errors. I still have the compile stuff in msys and the
>>copy in c:\pgsql so that explains why it is picking it up twice I
>>guess. In any case I still have the error I first asked about last
>>week.
>>
>>
>
>What parameters did you run configure with?
>
>cheers
>
>andrew
>
>
>
>
>>Regards
>>
>>Richard
>>
>>-----Original Message-----
>>From: pgsql-hackers-win32-owner(at)postgresql(dot)org
>>[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
>>Dunstan
>>Sent: Thursday, 13 May 2004 8:54 PM
>>To: pgsql-hackers-win32(at)postgresql(dot)org
>>Subject: Re: [pgsql-hackers-win32] Runtime Problems
>>
>>
>>I said:
>>
>>
>>>Richard Luckhurst said:
>>>
>>>
>>>>Hello All
>>>>
>>>>I am quite new to pgsql and the Win32 port. I have just tried
>>>>Vishal's new guide to building
>>>>and I am having what looks like a path problem when I try to
>>>>initialise a database. I am using
>>>>Windows 2000. Everything builds and installs OK and I have copied the
>>>>files in the msys\1.0\local\pgsql
>>>>to my c:\pgsql folder as per the instructions. I have added
>>>>C:\pgsql\bin and c:\pgsql\lib to my path
>>>>as instructed. When I try to run initdb I get the following error
>>>>
>>>>initdb -D c:\pgsql\data -W --lc-collate=C
>>>>
>>>>
>>The clue is actually in these following 4 lines
>>
>>
>>
>>>>Bad command or file name
>>>>fgets failure: No error
>>>>Bad command or file name
>>>>fgets failure: No error
>>>>
>>>>
>>For some reason, initdb has found postgres.exe in 2 locations but in
>>both cases has been unable to execute it, and consequently unable to
>>read in the version string.
>>
>>That's a bit strange - I have no explanation for it right now.
>>
>>The relevant code has just been refactored by Bruce as part of the
>>relocation stuff.
>>
>>For now, I still recommend running from the installed path.
>>
>>cheers
>>
>>andrew
>>
>>
>>
>>
>>>>The program "postgres" is needed by initdb but was not found in the
>>>>directory "C:/msys/1.0/local/pgsql/bin". Check your installation
>>>>
>>>>I would appreciate any clues here as this has me stumped. I don't
>>>>understand why is should even be looking in the msys directory.
>>>>
>>>>
>>>>
>>>I haven't had time to read the document referred to, but if it
>>>currently recommends that you run from anywhere but the installed path
>>>then I disagree with it. When we get relocatable installs, which Bruce
>>>is working on, you will be able to move the whole installation around
>>>to your heart's content.
>>>
>>>Have you checked that there is still in fact a
>>>C:/msys/1.0/local/pgsql/bin/postgres.exe? Could it be a permissions
>>>problem?
>>>
>>>
>>>
>>
>>
>
>
>
>
>---------------------------(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
>
>
>__________ NOD32 1.762 (20040516) Information __________
>
>This message was checked by NOD32 antivirus system.
>http://www.nod32.com
>
>
>
>

__________ NOD32 1.762 (20040516) Information __________

This message was checked by NOD32 antivirus system.
http://www.nod32.com

Richard Luckhurst said:
> Hi Andrew
>
> if I try to just run bin/initdb in the pgsql directory I get the normal
> error

sorry - of course I meant

bin\initdb -D c:\pgsql\data -W --lc-collate=C

> that bin is not an executable. If I try the full path
> c:\pgsql\bin\initdb I get the same old error.
>
> Regards
>
> Richard
>
> -----Original Message-----
> From: Andrew Dunstan [mailto:andrew(at)dunslane(dot)net]
> Sent: Monday, 17 May 2004 9:42 AM
> To: Richard Luckhurst
> Cc: PGSQL Hackers
> Subject: Re: [pgsql-hackers-win32] Runtime Problems
>
>
>
>
> Richard Luckhurst wrote:
>
>>Hi Andrew
>>
>>I ran configure with the --without-zlib option
>>
>
> What happens if you cd to c:\pgsql and run
>
> bin/initdb -D c:\pgsql\data -W --lc-collate=C
>
> ?
>
> cheers
>
> andrew
>
>
>>
>>Regards
>>
>>Richard
>>
>>-----Original Message-----
>>From: pgsql-hackers-win32-owner(at)postgresql(dot)org
>>[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
>>Dunstan
>>Sent: Sunday, 16 May 2004 8:13 PM
>>To: pgsql-hackers-win32(at)postgresql(dot)org
>>Subject: Re: [pgsql-hackers-win32] Runtime Problems
>>
>>
>>Richard Luckhurst said:
>>
>>
>>>Hi All
>>>
>>>I have just recompiled using the latest snapshot and I am still
>>>getting exactly the same errors. I still have the compile stuff in
>>>msys and the copy in c:\pgsql so that explains why it is picking it up
>>>twice I guess. In any case I still have the error I first asked about
>>>last week.
>>>
>>>
>>
>>What parameters did you run configure with?
>>
>>cheers
>>
>>andrew
>>
>>
>>
>>
>>>Regards
>>>
>>>Richard
>>>
>>>-----Original Message-----
>>>From: pgsql-hackers-win32-owner(at)postgresql(dot)org
>>>[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
>>>Dunstan
>>>Sent: Thursday, 13 May 2004 8:54 PM
>>>To: pgsql-hackers-win32(at)postgresql(dot)org
>>>Subject: Re: [pgsql-hackers-win32] Runtime Problems
>>>
>>>
>>>I said:
>>>
>>>
>>>>Richard Luckhurst said:
>>>>
>>>>
>>>>>Hello All
>>>>>
>>>>>I am quite new to pgsql and the Win32 port. I have just tried
>>>>>Vishal's new guide to building
>>>>>and I am having what looks like a path problem when I try to
>>>>>initialise a database. I am using
>>>>>Windows 2000. Everything builds and installs OK and I have copied
>>>>>the files in the msys\1.0\local\pgsql
>>>>>to my c:\pgsql folder as per the instructions. I have added
>>>>>C:\pgsql\bin and c:\pgsql\lib to my path
>>>>>as instructed. When I try to run initdb I get the following error
>>>>>
>>>>>initdb -D c:\pgsql\data -W --lc-collate=C
>>>>>
>>>>>
>>>The clue is actually in these following 4 lines
>>>
>>>
>>>
>>>>>Bad command or file name
>>>>>fgets failure: No error
>>>>>Bad command or file name
>>>>>fgets failure: No error
>>>>>
>>>>>
>>>For some reason, initdb has found postgres.exe in 2 locations but in
>>>both cases has been unable to execute it, and consequently unable to
>>>read in the version string.
>>>
>>>That's a bit strange - I have no explanation for it right now.
>>>
>>>The relevant code has just been refactored by Bruce as part of the
>>>relocation stuff.
>>>
>>>For now, I still recommend running from the installed path.
>>>
>>>cheers
>>>
>>>andrew
>>>
>>>
>>>
>>>
>>>>>The program "postgres" is needed by initdb but was not found in the
>>>>>directory "C:/msys/1.0/local/pgsql/bin". Check your installation
>>>>>
>>>>>I would appreciate any clues here as this has me stumped. I don't
>>>>>understand why is should even be looking in the msys directory.
>>>>>
>>>>>
>>>>>
>>>>I haven't had time to read the document referred to, but if it
>>>>currently recommends that you run from anywhere but the installed
>>>>path then I disagree with it. When we get relocatable installs, which
>>>>Bruce is working on, you will be able to move the whole installation
>>>>around to your heart's content.
>>>>
>>>>Have you checked that there is still in fact a
>>>>C:/msys/1.0/local/pgsql/bin/postgres.exe? Could it be a permissions
>>>>problem?
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>>---------------------------(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
>>
>>
>>__________ NOD32 1.762 (20040516) Information __________
>>
>>This message was checked by NOD32 antivirus system.
>>http://www.nod32.com
>>
>>
>>
>>
>
>
>
> __________ NOD32 1.762 (20040516) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.nod32.com

Hi Andrew

I get the same old fgets error.

Regards

Richard

-----Original Message-----
From: Andrew Dunstan [mailto:andrew(at)dunslane(dot)net]
Sent: Monday, 17 May 2004 12:32 PM
To: rickl(at)soundadvice(dot)aunz(dot)net
Cc: pgsql-hackers-win32(at)postgresql(dot)org
Subject: RE: [pgsql-hackers-win32] Runtime Problems

Richard Luckhurst said:
> Hi Andrew
>
> if I try to just run bin/initdb in the pgsql directory I get the normal
> error

sorry - of course I meant

bin\initdb -D c:\pgsql\data -W --lc-collate=C

> that bin is not an executable. If I try the full path
> c:\pgsql\bin\initdb I get the same old error.
>
> Regards
>
> Richard
>
> -----Original Message-----
> From: Andrew Dunstan [mailto:andrew(at)dunslane(dot)net]
> Sent: Monday, 17 May 2004 9:42 AM
> To: Richard Luckhurst
> Cc: PGSQL Hackers
> Subject: Re: [pgsql-hackers-win32] Runtime Problems
>
>
>
>
> Richard Luckhurst wrote:
>
>>Hi Andrew
>>
>>I ran configure with the --without-zlib option
>>
>
> What happens if you cd to c:\pgsql and run
>
> bin/initdb -D c:\pgsql\data -W --lc-collate=C
>
> ?
>
> cheers
>
> andrew
>
>
>>
>>Regards
>>
>>Richard
>>
>>-----Original Message-----
>>From: pgsql-hackers-win32-owner(at)postgresql(dot)org
>>[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
>>Dunstan
>>Sent: Sunday, 16 May 2004 8:13 PM
>>To: pgsql-hackers-win32(at)postgresql(dot)org
>>Subject: Re: [pgsql-hackers-win32] Runtime Problems
>>
>>
>>Richard Luckhurst said:
>>
>>
>>>Hi All
>>>
>>>I have just recompiled using the latest snapshot and I am still
>>>getting exactly the same errors. I still have the compile stuff in
>>>msys and the copy in c:\pgsql so that explains why it is picking it up
>>>twice I guess. In any case I still have the error I first asked about
>>>last week.
>>>
>>>
>>
>>What parameters did you run configure with?
>>
>>cheers
>>
>>andrew
>>
>>
>>
>>
>>>Regards
>>>
>>>Richard
>>>
>>>-----Original Message-----
>>>From: pgsql-hackers-win32-owner(at)postgresql(dot)org
>>>[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Andrew
>>>Dunstan
>>>Sent: Thursday, 13 May 2004 8:54 PM
>>>To: pgsql-hackers-win32(at)postgresql(dot)org
>>>Subject: Re: [pgsql-hackers-win32] Runtime Problems
>>>
>>>
>>>I said:
>>>
>>>
>>>>Richard Luckhurst said:
>>>>
>>>>
>>>>>Hello All
>>>>>
>>>>>I am quite new to pgsql and the Win32 port. I have just tried
>>>>>Vishal's new guide to building
>>>>>and I am having what looks like a path problem when I try to
>>>>>initialise a database. I am using
>>>>>Windows 2000. Everything builds and installs OK and I have copied
>>>>>the files in the msys\1.0\local\pgsql
>>>>>to my c:\pgsql folder as per the instructions. I have added
>>>>>C:\pgsql\bin and c:\pgsql\lib to my path
>>>>>as instructed. When I try to run initdb I get the following error
>>>>>
>>>>>initdb -D c:\pgsql\data -W --lc-collate=C
>>>>>
>>>>>
>>>The clue is actually in these following 4 lines
>>>
>>>
>>>
>>>>>Bad command or file name
>>>>>fgets failure: No error
>>>>>Bad command or file name
>>>>>fgets failure: No error
>>>>>
>>>>>
>>>For some reason, initdb has found postgres.exe in 2 locations but in
>>>both cases has been unable to execute it, and consequently unable to
>>>read in the version string.
>>>
>>>That's a bit strange - I have no explanation for it right now.
>>>
>>>The relevant code has just been refactored by Bruce as part of the
>>>relocation stuff.
>>>
>>>For now, I still recommend running from the installed path.
>>>
>>>cheers
>>>
>>>andrew
>>>
>>>
>>>
>>>
>>>>>The program "postgres" is needed by initdb but was not found in the
>>>>>directory "C:/msys/1.0/local/pgsql/bin". Check your installation
>>>>>
>>>>>I would appreciate any clues here as this has me stumped. I don't
>>>>>understand why is should even be looking in the msys directory.
>>>>>
>>>>>
>>>>>
>>>>I haven't had time to read the document referred to, but if it
>>>>currently recommends that you run from anywhere but the installed
>>>>path then I disagree with it. When we get relocatable installs, which
>>>>Bruce is working on, you will be able to move the whole installation
>>>>around to your heart's content.
>>>>
>>>>Have you checked that there is still in fact a
>>>>C:/msys/1.0/local/pgsql/bin/postgres.exe? Could it be a permissions
>>>>problem?
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>>---------------------------(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
>>
>>
>>__________ NOD32 1.762 (20040516) Information __________
>>
>>This message was checked by NOD32 antivirus system.
>>http://www.nod32.com
>>
>>
>>
>>
>
>
>
> __________ NOD32 1.762 (20040516) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.nod32.com

__________ NOD32 1.762 (20040516) Information __________

This message was checked by NOD32 antivirus system.
http://www.nod32.com

Richard Luckhurst wrote:
> Hi Andrew
>
> I get the same old fgets error.

That error is from a copy of CVS that is perhaps a few weeks old:

>>>>>Bad command or file name
>>>>>fgets failure: No error
>>>>>Bad command or file name
>>>>>fgets failure: No error

I have fixed it and it shouldn't appear in current CVS.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

Hi Bruce

I am working from a snapshot only 2 days old. Is the snapshot no good?

Regards

Richard

-----Original Message-----
From: pgsql-hackers-win32-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-win32-owner(at)postgresql(dot)org]On Behalf Of Bruce
Momjian
Sent: Monday, 17 May 2004 1:54 PM
To: Richard Luckhurst
Cc: Andrew Dunstan; PGSQL Hackers
Subject: Re: [pgsql-hackers-win32] Runtime Problems

Richard Luckhurst wrote:
> Hi Andrew
>
> I get the same old fgets error.

That error is from a copy of CVS that is perhaps a few weeks old:

>>>>>Bad command or file name
>>>>>fgets failure: No error
>>>>>Bad command or file name
>>>>>fgets failure: No error

I have fixed it and it shouldn't appear in current CVS.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

__________ NOD32 1.762 (20040516) Information __________

This message was checked by NOD32 antivirus system.
http://www.nod32.com

Richard Luckhurst wrote:
> Hi Bruce
>
> I am working from a snapshot only 2 days old. Is the snapshot no good?

That new, huh? It should be fine. I assume the errors are coming from
src/port/exec.c. Can you add some printf's in there to see where it is
failing?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

Bruce Momjian said:
> Richard Luckhurst wrote:
>> Hi Bruce
>>
>> I am working from a snapshot only 2 days old. Is the snapshot no good?
>
> That new, huh? It should be fine. I assume the errors are coming from
> src/port/exec.c. Can you add some printf's in there to see where it is
> failing?
>

In particular, we need to see the command line that is being passed to
popen() - that's apparently where it is failing.

cheers

andrew