Open Source Database Summit

Bruce Momjian <pgman@candle.pha.pa.us> writes:

Tom Lane and I will be speaking at the Open Source Database Summit,
October 30 and 31, in San Jose, California.

For anyone who's interested, copies of the slides for my presentations
are up in PDF format at http://www.postgresql.org/osdn/index.html.

Bruce hasn't done his slides yet ;-)

regards, tom lane

Bruce Momjian <pgman@candle.pha.pa.us> writes:

Tom Lane and I will be speaking at the Open Source Database Summit,
October 30 and 31, in San Jose, California.

For anyone who's interested, copies of the slides for my presentations
are up in PDF format at http://www.postgresql.org/osdn/index.html.

Bruce hasn't done his slides yet ;-)

OK, mine slides are done, and are at the same URL, titled "History of
PostgreSQL Open-Source Development".

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

If we try to run a perl script which accesses a Postgres dB using mod_perl
with Apache we get:
"child pid 25144 exit signal Segmentation fault (11)
Out of memory!"

The scripts work fine when used w/o mod_perl, and other non-Postgres
scripts wotk OK with mod_perl.

What are we doing wrong?

Thanks

Steve

--
thorNET - Internet Consultancy, Services & Training
Phone: 01454 854413
Fax: 01454 854412
http://www.thornet.co.uk

See mod_perl guide for debugging apache, such as getting a traceback at
the time of crash, and using strace to see what the script was doing
before dying.

Also, upgrade to latest DBD::Pg, there were a few small crashes which got
fixed.

-alex

On Fri, 20 Oct 2000, Steve Heaven wrote:

And of course you could have just run out of memory! Storing really large
result sets is a good way to do that... :-)

-Mitch

----- Original Message -----
From: "Alex Pilosov" <alex@pilosoft.com>
To: "Steve Heaven" <steve@thornet.co.uk>
Cc: <pgsql-general@postgresql.org>
Sent: Friday, October 20, 2000 7:28 AM
Subject: Re: [GENERAL] Out of memory errors with mod_perl

See mod_perl guide for debugging apache, such as getting a traceback at
the time of crash, and using strace to see what the script was doing
before dying.

Also, upgrade to latest DBD::Pg, there were a few small crashes which got
fixed.

-alex

On Fri, 20 Oct 2000, Steve Heaven wrote:

If we try to run a perl script which accesses a Postgres dB using

mod_perl

At 08:46 20/10/00 -0700, Mitch Vincent wrote:

And of course you could have just run out of memory! Storing really large
result sets is a good way to do that... :-)

No, the problem occurs as soon as the script runs. Even if we set up small
dummy scripts that hardly do anything it still crashes.

Steve

--
thorNET - Internet Consultancy, Services & Training
Phone: 01454 854413
Fax: 01454 854412
http://www.thornet.co.uk

Steve Heaven <steve@thornet.co.uk> writes:

If we try to run a perl script which accesses a Postgres dB using mod_perl
with Apache we get:
"child pid 25144 exit signal Segmentation fault (11)
Out of memory!"

I am mighty ignorant about Apache, but I'll venture a bet that the "Out
of memory!" message is a red herring. It could easily be coming from
some clueless bit of code that prints that in response to *any* failure.

The thing that looks real to me is the report that a child process died
with a SEGV signal. You should go look for the resulting corefile and
see if you can get a backtrace from it. For that matter, do you even
know what program the child process was running?

regards, tom lane

Hi,

I've got this very bad message with Apache 1.3.6 running mod_perl and
postgresql
6.3.2 with a site hosted by an ISP. They just allocate a max of 10 Mo of memory
for
each user.

For me this was a message coming from server resources. Not enougth memory.
At home with the same configuration I never met this problem, but it's my home
:-)

To fix it I just changed my ISP ! Other thing, as I remember if you are running
mod_perl
prior of 1.21 there is leak of memory, in Perl before 5.005_3 also.

What are the versions of your environment (Apache, mod_perl, Postgres and Perl)
?

Tom Lane wrote: