> Nigel J. Andrews wrote:
>
> On Wed, 24 Sep 2003, shreedhar wrote:
>
> > I am using PHP4 as client side.
>
> In that case what about this setting in php.ini:
>
> memory_limit = 8M ; Maximum amount of memory a script
> may consume (8MB)
But before you change that, you may want to dive into the code that
consumes so much memory. Perhaps you just don't reuse/free enough memory
or have a bug in your code that causes it to loop too often.
But as said, it has nothing to do with postgres and is a pure php error
and you may want to continue your quest on the php mailing lists or
their pretty decent manual.
Regards,
Arjen
> > ----- Original Message -----
> > From: "Tom Lane" <tgl@sss.pgh.pa.us>
> > To: "shreedhar" <shreedhar@lucidindia.net>
> > Cc: "Postgre General" <pgsql-general@postgresql.org>;
> "Postgre Admin"
> > <pgsql-admin@postgresql.org>
> > Sent: Wednesday, September 24, 2003 10:44 AM
> > Subject: Re: [ADMIN] Fatal error: Allowed memory size of
> 8388608 bytes
> > exhausted
> >
> >
> > > "shreedhar" <shreedhar@lucidindia.net> writes:
> > > > If I try to insert I got the following error as
> > > > Fatal error: Allowed memory size of 8388608 bytes
> exhausted (tried
> > > > to allocate 79 bytes)
> > >
> > > There is not, and never has been, any error message of
> that wording
> > > in the PG backend. You must be looking at some
> client-side failure.
> > > But since you didn't tell us what client-side code you're using,
> > > it's hard to say more than that...
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>