Skip site navigation (1) Skip section navigation (2)

Re: BUG #5267: initdb fails on AIX: could not identify current directory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Felt <mamfelt(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5267: initdb fails on AIX: could not identify current directory
Date: 2010-01-07 16:42:56
Message-ID: 26533.1262882576@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Michael Felt <mamfelt(at)gmail(dot)com> writes:
> I ran my test program with larger and smaller MAXPGPATH constants. 2046
> (1023 * 2) was the largest I tested and it worked fine. When it was shorted
> the call failed. I did not test the error message.

[ scratches head... ]  This seems to be misbehavior of getcwd() itself,
since the paths involved are certainly not 2K long.
Perhaps you need to file a bug with IBM.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Robert HaasDate: 2010-01-07 18:01:47
Subject: Re: BUG #5268: PQgetvalue incorrectly returns 0
Previous:From: Tom LaneDate: 2010-01-07 16:39:59
Subject: Re: BUG #5267: initdb fails on AIX: could not identify current directory

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group