Обсуждение: PostgreSQL 7.1 beta3 on Windows 2k
Hi everyone,
I had PostgreSQL 7.0.3 installed on my system, but I had the memory detach
problem so I decided to upgrade to 7.1 beta 3 instead of patching.
With this I mean Cygwin worked for PostgreSQL 7.0.3 port so it works.
Installation process for 7.1:
./configure --------- OK
make --------- NOT OK; the last lines in the output were:
make[2]: Entering directory `/usr/src/postgresql-7.1beta3/src/interfaces'
make[3]: Entering directory
`/usr/src/postgresql-7.1beta3/src/interfaces/libpq'
dlltool --export-all --output-def pq.def fe-auth.o fe-connect.o fe-exec.o
fe-mis
c.o fe-print.o fe-lobj.o pqexpbuffer.o dllist.o pqsignal.o
dllwrap -o pq.dll --dllname pq.dll --def pq.def fe-auth.o fe-connect.o
fe-exec.o
fe-misc.o fe-print.o fe-lobj.o pqexpbuffer.o dllist.o pqsignal.o
../../../src
/utils/dllinit.o -L/usr/local/lib -L/usr/local/lib -L../../../src/backend -
lpos
tgres -lcygipc -lcygwin -lcrypt -lkernel32 -lcrypt
../../../src/utils/dllinit.o(.text+0x102):dllinit.c: undefined reference to
`__i
mp_reent_data'
collect2: ld returned 1 exit status
dllwrap: gcc exited with status 1
make[3]: *** [libpq.a] Error 1
make[3]: Leaving directory
`/usr/src/postgresql-7.1beta3/src/interfaces/libpq'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/src/postgresql-7.1beta3/src/interfaces'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/postgresql-7.1beta3/src'
make: *** [all] Error 2
Suggestions & IDEAS much appreciated.
//Juan
Juan,
On Tue, Jan 30, 2001 at 02:12:56AM +0100, JJAR wrote:
> I had PostgreSQL 7.0.3 installed on my system, but I had the memory detach
> problem so I decided to upgrade to 7.1 beta 3 instead of patching.
> With this I mean Cygwin worked for PostgreSQL 7.0.3 port so it works.
>
> Installation process for 7.1:
>
> ./configure --------- OK
> make --------- NOT OK; the last lines in the output were:
PostgreSQL 7.1 beta 3 is known *not* to build OOTB for Cygwin but the
current snapshot and CVS does.
You can find the latest snapshot at:
ftp://ftp.postgresql.org/pub/dev/postgresql-snapshot.tar.gz
and CVS at:
http://www.postgresql.org/devel-corner/docs/postgres/cvs.htm#ANONCVS
Jason
--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com
Jason,
Thank you very much for the information.
But now I would like to know if I have to apply KevinLo's steps here, I
have tried the selfcontained instructions:
I mean I already have done:
./configure --- OK
make --- OK
make install --- OK
adduser postgres --- NOT OK ( command not found )
su - postgres --- NOT OK ( because the previous didn't work, I guess )
/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
in this final, the process, gets 100% of the CPU power for 6 minutes and
running...
The output:
$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
This database system will be initialized with username "administrador".
This user will own all the data files and must also own the server process.
Fixing permissions on existing directory /usr/local/pgsql/data
Creating directory /usr/local/pgsql/data/base
Creating directory /usr/local/pgsql/data/global
Creating directory /usr/local/pgsql/data/pg_xlog
Creating template1 database in /usr/local/pgsql/data/base/1
Do I have to apply KevinLo's steps, part or any variation on them.
Thank you in advance.
//Juan
-----Mensaje original-----
De: Jason Tishler [mailto:Jason.Tishler@dothill.com]
Enviado el: martes, 30 de enero de 2001 12:29
Para: JJAR
CC: pgsql-ports@postgresql.org
Asunto: Re: [PORTS] PostgreSQL 7.1 beta3 on Windows 2k
Juan,
On Tue, Jan 30, 2001 at 02:12:56AM +0100, JJAR wrote:
> I had PostgreSQL 7.0.3 installed on my system, but I had the memory
detach
> problem so I decided to upgrade to 7.1 beta 3 instead of patching.
> With this I mean Cygwin worked for PostgreSQL 7.0.3 port so it works.
>
> Installation process for 7.1:
>
> ./configure --------- OK
> make --------- NOT OK; the last lines in the output were:
PostgreSQL 7.1 beta 3 is known *not* to build OOTB for Cygwin but the
current snapshot and CVS does.
You can find the latest snapshot at:
ftp://ftp.postgresql.org/pub/dev/postgresql-snapshot.tar.gz
and CVS at:
http://www.postgresql.org/devel-corner/docs/postgres/cvs.htm#ANONCVS
Jason
--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com
Juan, On Wed, Jan 31, 2001 at 01:45:32AM +0100, JJAR wrote: > Thank you very much for the information. Your welcome. > But now I would like to know if I have to apply KevinLo's steps here, I > have tried the selfcontained instructions: > I mean I already have done: > > ./configure --- OK > make --- OK > make install --- OK > adduser postgres --- NOT OK ( command not found ) > su - postgres --- NOT OK ( because the previous didn't work, I guess ) > /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data > > in this final, the process, gets 100% of the CPU power for 6 minutes and > running... > ... From a subsequent post of yours, I will assume that you solved your problems yourself -- sorry that I was not able to offer you prompt assistance regarding this matter. Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com Hazlet, NJ 07730 USA WWW: http://www.dothill.com
Jason,
Maybe it a was a failure on my side not beginnig a new thread for this
question, but I felt spawning a new thread was not the right thing.
I still have this problem.
I have tried to compile again from scratch and trying "make check" before
installing.
This is the output:
============== running regression test queries ==============
parallel group (13 tests): boolean char name text varchar int2 oid int4
int8 fl
oat4 float8 bit numeric
boolean ... ok
char ... ok
name ... ok
varchar ... ok
text ... ok
int2 ... ok
int4 ... ok
int8 ... ok
oid ... ok
float4 ... ok
float8 ... ok
bit ... ok
numeric ... ok
test strings ... ok
test numerology ... ok
parallel group (18 tests): point lseg box path polygon circle date time
inet oi
djoins timestamp
I come to this point and nothing happens. The CPU doesn't work at all ( only
5% CPU power consumption ) and the hard disk is quiet so the process is
dead.
If you ( or anyone ) have any ideas about this tell me please.
Thank you in advance.
//Juan
-----Mensaje original-----
De: Jason Tishler [mailto:Jason.Tishler@dothill.com]
Enviado el: lunes, 05 de febrero de 2001 20:23
Para: JJAR
CC: pgsql-ports@postgresql.org
Asunto: Re: [PORTS] PostgreSQL 7.1 beta3 on Windows 2k
Juan,
On Wed, Jan 31, 2001 at 01:45:32AM +0100, JJAR wrote:
> Thank you very much for the information.
Your welcome.
> But now I would like to know if I have to apply KevinLo's steps here, I
> have tried the selfcontained instructions:
> I mean I already have done:
>
> ./configure --- OK
> make --- OK
> make install --- OK
> adduser postgres --- NOT OK ( command not found )
> su - postgres --- NOT OK ( because the previous didn't work, I
guess )
> /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
>
> in this final, the process, gets 100% of the CPU power for 6 minutes and
> running...
> ...
From a subsequent post of yours, I will assume that you solved your
problems yourself -- sorry that I was not able to offer you prompt
assistance regarding this matter.
Jason
--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com
"JJAR" <jjarcore@eresmas.com> writes:
> [ parallel regression tests hang up in second parallel group ]
> I come to this point and nothing happens. The CPU doesn't work at all ( only
> 5% CPU power consumption ) and the hard disk is quiet so the process is
> dead.
Hmm. You might be looking at a shell bug. There are shells out there
that lose track of how many children they have when asked to spawn more
than a dozen or so parallel children. For example, I see extremely
similar behavior when I try to run 'make check' using the standard
/bin/sh shell on HPUX 10.20: it locks up partway through the second set
of parallel tests. I have to select SHELL=/bin/ksh instead to get
the tests to complete. I'm not sure it's quite the same issue, because
HPUX's sh goes to 100% CPU usage after getting confused in this way,
but it still seems like a likely explanation.
Can you run the non-parallel test (make installcheck) successfully?
Also, try splitting the parallel groups in the parallel_schedule file
into smaller numbers of tests.
regards, tom lane
Juan,
On Mon, Feb 05, 2001 at 10:41:55PM +0100, JJAR wrote:
> Maybe it a was a failure on my side not beginnig a new thread for this
> question, but I felt spawning a new thread was not the right thing.
> I still have this problem.
> I have tried to compile again from scratch and trying "make check" before
> installing.
> This is the output:
>
> ============== running regression test queries ==============
> parallel group (13 tests): boolean char name text varchar int2 oid int4
> int8 float4 float8 bit numeric
> ...
> parallel group (18 tests): point lseg box path polygon circle date time
> inet oi djoins timestamp
>
> I come to this point and nothing happens. The CPU doesn't work at all ( only
> 5% CPU power consumption ) and the hard disk is quiet so the process is
> dead.
>
> If you ( or anyone ) have any ideas about this tell me please.
> Thank you in advance.
Please see item #2 in the following:
http://postgresql.readysetnet.com/mhonarc/pgsql-ports/2001-01/msg00066.html
Does any of that description match your environment and observations?
If so, then upgrade your machine (i.e., physical memory and swap space).
Jason
--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com
Hi Tom,
I have tried "make installcheck" and this is the output I get:
$ make installcheck
make -C src/test installcheck
make[1]: Entering directory `/usr/src/postgresql-snapshot/src/test'
make -C regress installcheck
make[2]: Entering directory `/usr/src/postgresql-snapshot/src/test/regress'
make -C ../../../contrib/spi REFINT_VERBOSE=1 refint.dll autoinc.dll
make[3]: Entering directory `/usr/src/postgresql-snapshot/contrib/spi'
make[3]: `refint.dll' is up to date.
make[3]: `autoinc.dll' is up to date.
make[3]: Leaving directory `/usr/src/postgresql-snapshot/contrib/spi'
sh.exe ./pg_regress --schedule=./serial_schedule --multibyte=
(using postmaster on Unix socket, default port)
============== dropping database "regression" ==============
psql: connectDBStart() -- connect() failed: No such file or directory
Is the postmaster running at 'localhost'
and accepting connections on Unix socket '5432'?
dropdb: database removal failed
============== creating database "regression" ==============
psql: connectDBStart() -- connect() failed: No such file or directory
Is the postmaster running at 'localhost'
and accepting connections on Unix socket '5432'?
createdb: database creation failed
pg_regress: createdb failed
make[2]: Leaving directory `/usr/src/postgresql-snapshot/src/test/regress'
make[1]: Leaving directory `/usr/src/postgresql-snapshot/src/test'
Maybe there is an additional step I have not completed. If it is let me
know.
Thank you fot your time.
//Juan
-----Mensaje original-----
De: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Enviado el: martes, 06 de febrero de 2001 2:14
Para: JJAR
CC: Jason Tishler; pgsql-ports@postgresql.org
Asunto: Re: [PORTS] PostgreSQL 7.1 beta3 on Windows 2k
"JJAR" <jjarcore@eresmas.com> writes:
> [ parallel regression tests hang up in second parallel group ]
> I come to this point and nothing happens. The CPU doesn't work at all (
only
> 5% CPU power consumption ) and the hard disk is quiet so the process is
> dead.
Hmm. You might be looking at a shell bug. There are shells out there
that lose track of how many children they have when asked to spawn more
than a dozen or so parallel children. For example, I see extremely
similar behavior when I try to run 'make check' using the standard
/bin/sh shell on HPUX 10.20: it locks up partway through the second set
of parallel tests. I have to select SHELL=/bin/ksh instead to get
the tests to complete. I'm not sure it's quite the same issue, because
HPUX's sh goes to 100% CPU usage after getting confused in this way,
but it still seems like a likely explanation.
Can you run the non-parallel test (make installcheck) successfully?
Also, try splitting the parallel groups in the parallel_schedule file
into smaller numbers of tests.
regards, tom lane
Hi Jason,
No problem with the configuration I think.
Processor: PII 400Mhz
RAM: 256 MB
Swap: initial 384 MB
max 768 MB
//Juan
-----Mensaje original-----
De: Jason Tishler [mailto:Jason.Tishler@dothill.com]
Enviado el: martes, 06 de febrero de 2001 3:18
Para: JJAR
CC: pgsql-ports@postgresql.org
Asunto: Re: [PORTS] PostgreSQL 7.1 beta3 on Windows 2k
Juan,
On Mon, Feb 05, 2001 at 10:41:55PM +0100, JJAR wrote:
> Maybe it a was a failure on my side not beginnig a new thread for this
> question, but I felt spawning a new thread was not the right thing.
> I still have this problem.
> I have tried to compile again from scratch and trying "make check" before
> installing.
> This is the output:
>
> ============== running regression test queries ==============
> parallel group (13 tests): boolean char name text varchar int2 oid int4
> int8 float4 float8 bit numeric
> ...
> parallel group (18 tests): point lseg box path polygon circle date time
> inet oi djoins timestamp
>
> I come to this point and nothing happens. The CPU doesn't work at all (
only
> 5% CPU power consumption ) and the hard disk is quiet so the process is
> dead.
>
> If you ( or anyone ) have any ideas about this tell me please.
> Thank you in advance.
Please see item #2 in the following:
http://postgresql.readysetnet.com/mhonarc/pgsql-ports/2001-01/msg00066.html
Does any of that description match your environment and observations?
If so, then upgrade your machine (i.e., physical memory and swap space).
Jason
--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com
"JJAR" <jjarcore@eresmas.com> writes:
> I have tried "make installcheck" and this is the output I get:
> ============== dropping database "regression" ==============
> psql: connectDBStart() -- connect() failed: No such file or directory
> Is the postmaster running at 'localhost'
> and accepting connections on Unix socket '5432'?
> dropdb: database removal failed
> ============== creating database "regression" ==============
> psql: connectDBStart() -- connect() failed: No such file or directory
> Is the postmaster running at 'localhost'
> and accepting connections on Unix socket '5432'?
> createdb: database creation failed
> pg_regress: createdb failed
> Maybe there is an additional step I have not completed.
Installing and starting the postmaster, looks like ...
regards, tom lane
Tom,
I have downloaded PostgreSQL 7.1 beta4 and I have tried the regression
tests with "make check", they run until 13 parallel tests or so ( with 13
does with 16 does not ) when it stops you can make it continue killing some
processes with the task manager, but I think this would be the same if
something inherently bad were happenning within the process.
I have tried "make installcheck" and in the end I get this:
############################################################################
############################
ok
======================
All 76 tests passed.
======================
make[2]: Leaving directory `/usr/src/postgresql-7.1beta4/src/test/regress'
make[1]: Leaving directory `/usr/src/postgresql-7.1beta4/src/test'
############################################################################
############################
but I have seen the word ERROR before this, so I am wondering why. An
example of this:
############################################################################
############################
============== running regression test queries ==============
test boolean ... ERROR: Bad boolean external representation
'XXX'
ok
test char ... ok
test name ... ok
test varchar ... ok
test text ... ok
test int2 ... ERROR: pg_atoi: error in "34.5": can't parse
".5"
ERROR: pg_atoi: error reading "100000": Math result out of range
ERROR: pg_atoi: error in "asdf": can't parse "asdf"
ok
test int4 ... ERROR: pg_atoi: error in "34.5": can't parse
".5"
ERROR: pg_atoi: error reading "1000000000000": Math result out of range
ERROR: pg_atoi: error in "asdf": can't parse "asdf"
ok
test int8 ... ok
test oid ... ERROR: oidin: error in "asdfasd": can't parse
"as
dfasd"
ERROR: oidin: error in "99asdfasd": can't parse "asdfasd"
ok
test float4 ... ERROR: Bad float4 input format -- overflow
ERROR: Bad float4 input format -- overflow
ERROR: Bad float4 input format -- underflow
ERROR: Bad float4 input format -- underflow
ERROR: float4div: divide by zero error
ok
test float8 ... ERROR: Bad float8 input format -- overflow
ERROR: pow() result is out of range
ERROR: can't take log of zero
ERROR: can't take log of a negative number
ERROR: exp() result is out of range
ERROR: float8div: divide by zero error
ERROR: Input '10e400' is out of range for float8
ERROR: Input '-10e400' is out of range for float8
############################################################################
############################
Could you tell me if this is wrong or not please.
Thank you for your time.
//Juan
-----Mensaje original-----
De: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Enviado el: martes, 06 de febrero de 2001 2:14
Para: JJAR
CC: Jason Tishler; pgsql-ports@postgresql.org
Asunto: Re: [PORTS] PostgreSQL 7.1 beta3 on Windows 2k
"JJAR" <jjarcore@eresmas.com> writes:
> [ parallel regression tests hang up in second parallel group ]
> I come to this point and nothing happens. The CPU doesn't work at all (
only
> 5% CPU power consumption ) and the hard disk is quiet so the process is
> dead.
Hmm. You might be looking at a shell bug. There are shells out there
that lose track of how many children they have when asked to spawn more
than a dozen or so parallel children. For example, I see extremely
similar behavior when I try to run 'make check' using the standard
/bin/sh shell on HPUX 10.20: it locks up partway through the second set
of parallel tests. I have to select SHELL=/bin/ksh instead to get
the tests to complete. I'm not sure it's quite the same issue, because
HPUX's sh goes to 100% CPU usage after getting confused in this way,
but it still seems like a likely explanation.
Can you run the non-parallel test (make installcheck) successfully?
Also, try splitting the parallel groups in the parallel_schedule file
into smaller numbers of tests.
regards, tom lane
Juan, On Tue, Feb 06, 2001 at 08:13:42PM +0100, JJAR wrote: > No problem with the configuration I think. > > Processor: PII 400Mhz > RAM: 256 MB > Swap: initial 384 MB > max 768 MB Agreed. Sorry, but I don't what *is* causing your problem though... Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com Hazlet, NJ 07730 USA WWW: http://www.dothill.com
"JJAR" <jjarcore@eresmas.com> writes:
> I have tried "make installcheck" and in the end I get this:
> ======================
> All 76 tests passed.
> ======================
That looks good.
> but I have seen the word ERROR before this, so I am wondering why. An
> example of this:
> ============== running regression test queries ==============
> test boolean ... ERROR: Bad boolean external representation
> 'XXX'
> ok
I think you have started the postmaster in a way that left its stderr
going to your terminal, rather than redirected into a logfile. Those
look like the errors that the regression tests normally provoke --- but
as a rule, you don't want the logfile going to your screen.
Bottom line appears to be that your system has trouble running more than
a few processes in parallel. Good 'ol Microsoft strikes again...
regards, tom lane
JJAR writes: > I have downloaded PostgreSQL 7.1 beta4 and I have tried the regression > tests with "make check", they run until 13 parallel tests or so ( with 13 > does with 16 does not ) when it stops you can make it continue killing some > processes with the task manager, but I think this would be the same if > something inherently bad were happenning within the process. You might want to try running make SHELL=/bin/bash check (or whereever you have bash) because the standard /bin/sh is known to be pretty stupid. -- Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/
Peter, On Wed, Feb 07, 2001 at 06:08:58PM +0100, Peter Eisentraut wrote: > You might want to try running > > make SHELL=/bin/bash check > > (or whereever you have bash) because the standard /bin/sh is known to be > pretty stupid. On Cygwin, the "standard" sh is actually ash -- a stripped down bash that is suppose to be quicker at running scripts (e.g., configure). Nevertheless, I think that this is an excellent suggestion -- sh may be doing some goofy things so it is worth a shot. Juan, please try this and report back to the list -- I won't have access to the machine that had problems running the regression tests for a while. Thanks, Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com Hazlet, NJ 07730 USA WWW: http://www.dothill.com
Tom,
Thank you very much for your response.
Regards.
//Juan
-----Mensaje original-----
De: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Enviado el: miércoles, 07 de febrero de 2001 17:01
Para: JJAR
CC: Jason Tishler; pgsql-ports@postgresql.org
Asunto: Re: [PORTS] PostgreSQL 7.1 beta3 on Windows 2k
"JJAR" <jjarcore@eresmas.com> writes:
> I have tried "make installcheck" and in the end I get this:
> ======================
> All 76 tests passed.
> ======================
That looks good.
> but I have seen the word ERROR before this, so I am wondering why. An
> example of this:
> ============== running regression test queries ==============
> test boolean ... ERROR: Bad boolean external representation
> 'XXX'
> ok
I think you have started the postmaster in a way that left its stderr
going to your terminal, rather than redirected into a logfile. Those
look like the errors that the regression tests normally provoke --- but
as a rule, you don't want the logfile going to your screen.
Bottom line appears to be that your system has trouble running more than
a few processes in parallel. Good 'ol Microsoft strikes again...
regards, tom lane
Jason,
Well, I think you have read the response to Peter Eisentraut and the
previous e-mail to Tom Lane.
Tom says the database is OK so I have put it to work and have created a new
user, an empty database and have connected to it through JDBC. No problem by
the moment.
But ( there has always to be a but ) when I shutdown I get the
IpcMemoryDetach problem:
administrador@OBJECTIER /usr/local/pgsql/bin
$ pg_ctl stop
Smart Shutdown request at Wed Feb 7 22:20:33 2001
postmaster successfully shut down.
administrador@OBJECTIER /usr/local/pgsql/bin
$ DEBUG: shutting down
DEBUG: database system is shut down
IpcMemoryDetach: shmdt(0x70d0000) failed: Invalid argument
[2]+ Done postmaster -i (wd: /usr/local/pgsql/data)
(wd now: /usr/local/pgsql/bin)
The irony here is that I upgraded not to get this error. ;)
Thank you very much for your time and sorry if I have wasted it.
See you.
//Juan
-----Mensaje original-----
De: Jason Tishler [mailto:Jason.Tishler@dothill.com]
Enviado el: miercoles, 07 de febrero de 2001 19:13
Para: Peter Eisentraut
CC: JJAR; Tom Lane; pgsql-ports@postgresql.org
Asunto: Re: [PORTS] PostgreSQL 7.1 beta3 on Windows 2k
Peter,
On Wed, Feb 07, 2001 at 06:08:58PM +0100, Peter Eisentraut wrote:
> You might want to try running
>
> make SHELL=/bin/bash check
>
> (or whereever you have bash) because the standard /bin/sh is known to be
> pretty stupid.
On Cygwin, the "standard" sh is actually ash -- a stripped down bash
that is suppose to be quicker at running scripts (e.g., configure).
Nevertheless, I think that this is an excellent suggestion -- sh may be
doing some goofy things so it is worth a shot.
Juan, please try this and report back to the list -- I won't have access
to the machine that had problems running the regression tests for a while.
Thanks,
Jason
--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com
Hi Peter,
This is is the final output when it stop working.
============== creating temporary installation ==============
============== initializing database system ==============
============== starting postmaster ==============
running on port 65432 with pid 1796
============== creating database "regression" ==============
CREATE DATABASE
============== installing PL/pgSQL ==============
============== running regression test queries ==============
parallel group (13 tests): boolean char name varchar text int2 int4 int8
oid fl
oat4 bit
The CPU is free and the hard disk quiet.
Regards.
//Juan
-----Mensaje original-----
De: Peter Eisentraut [mailto:peter_e@gmx.net]
Enviado el: miercoles, 07 de febrero de 2001 18:09
Para: JJAR
CC: Tom Lane; Jason Tishler; pgsql-ports@postgresql.org
Asunto: RE: [PORTS] PostgreSQL 7.1 beta3 on Windows 2k
JJAR writes:
> I have downloaded PostgreSQL 7.1 beta4 and I have tried the regression
> tests with "make check", they run until 13 parallel tests or so ( with 13
> does with 16 does not ) when it stops you can make it continue killing
some
> processes with the task manager, but I think this would be the same if
> something inherently bad were happenning within the process.
You might want to try running
make SHELL=/bin/bash check
(or whereever you have bash) because the standard /bin/sh is known to be
pretty stupid.
--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/
Juan,
On Wed, Feb 07, 2001 at 11:28:06PM +0100, JJAR wrote:
> But ( there has always to be a but ) when I shutdown I get the
> IpcMemoryDetach problem:
Please see the following to solve the above problem:
http://postgresql.readysetnet.com/mhonarc/pgsql-ports/2001-01/msg00092.html
> The irony here is that I upgraded not to get this error. ;)
By upgraded do you mean upgraded Cygwin or PostgreSQL?
> Thank you very much for your time and sorry if I have wasted it.
Your welcome and no problem.
Jason
--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com