Hi, I posted this through the web page but it didn't come over the
list, so I am sending it directly. Hope that's okay.
I am able to get PostgreSQL 7.2.2 built and installed, and postmaster
starts up fine, but when hit with multiple simultaneous connections (2
or more), the server freezes
On Thursday, Sep 19, 2002, at 17:10 US/Eastern, Tom Lane wrote:
> Could you build with --enable-debug and --enable-cassert (if you didn't
> already), repeat the 'make check' scenario, and then attach to a few of
> the stuck backend processes with gdb and get stack traces from them?
> That would g
On Thursday, Sep 19, 2002, at 18:33 US/Eastern, Tom Lane wrote:
> David Christian <[EMAIL PROTECTED]> writes:
>> Happy to. Interestingly, when I build with --enable-debug and
>> --enable-cassert, the server doesn't lock up during 'make check', it
>>
On Friday, Sep 20, 2002, at 11:30 US/Eastern, Tom Lane wrote:
> If you are using "make check" then look for
> src/test/regress/tmp_check/data/base/*/core
Thanks. Here it is:
$ gdb src/test/regress/tmp_check/install/usr/local/pgsql/bin/postmaster
src/test/regress/tmp_check/data/base/16556/core
On Friday, Sep 20, 2002, at 11:30 US/Eastern, Tom Lane wrote:
> Another interesting line of attack would be to try compiling
> src/backend/storage/lmgr/lwlock.c at different optimization levels,
> to see if the problem goes away with less optimization. We saw a
> problem on AIX (if memory serves
I think you've fixed it. With your patch, and a simple
$ ./configure
$ make
$ make check
# make install
the check works and all tests (except geometry on floating point stuff)
pass; and after installing, I can really hammer the server and it
doesn't hang. Looks like users on Yellow Dog Linux
