Re: Out of memory errors with mod_perl - Mailing list pgsql-general

From Mitch Vincent
Subject Re: Out of memory errors with mod_perl
Date
Msg-id 005401c03aac$eb0dccf0$0200000a@doot
Whole thread Raw
In response to Re: Out of memory errors with mod_perl  (Alex Pilosov <alex@pilosoft.com>)
Responses Re: Out of memory errors with mod_perl  (Steve Heaven <steve@thornet.co.uk>)
List pgsql-general
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
> > 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
> >
> >
>
>


pgsql-general by date:

Previous
From: KuroiNeko
Date:
Subject: Re: MySQL -> pgsql
Next
From: Steve Heaven
Date:
Subject: Re: Out of memory errors with mod_perl