On Sunday, March 08, 2009, Tom Lane wrote:
> Carl Sopchak writes:
> > Here's what's around the error message in the log:
> >
> > SPI Proc: 3154128080 total in 398 blocks; 13664 free (178 chunks);
> > 3154114416 used
>
> Hmm, so apparently some internal leak within the plpgsql engine. I'd be
>
Carl Sopchak writes:
> Here's what's around the error message in the log:
> SPI Proc: 3154128080 total in 398 blocks; 13664 free (178 chunks);
> 3154114416 used
Hmm, so apparently some internal leak within the plpgsql engine. I'd be
willing to look into this if you can provide a self-conta
On Sunday, March 08, 2009, Tom Lane wrote:
> Carl Sopchak writes:
> > On Sunday, March 08, 2009, Gregory Stark wrote:
> >> What do you mean you're running out of memory?
> >
> > "ERROR: Out of Memory" is what I meant when I said I was running out of
> > memory! :-) This is returned by psql, but
On Sunday, March 08, 2009, Alvaro Herrera wrote:
> Carl Sopchak wrote:
> > Well, the upgrade to 8.3 seemed to rid me of the command limit, but now
> > I'm running out of memory. I have 2Gb physical and 8Gb swap (after
> > adding 4Gb).
>
> Do you have AFTER triggers on the involved tables? They ar
Carl Sopchak wrote on 08.03.2009 17:37:
or a way to run a function outside an implicit transaction
No sensible DBMS will let you do _anything_ outside a transaction
Thomas
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.
Carl Sopchak writes:
> On Sunday, March 08, 2009, Gregory Stark wrote:
>> What do you mean you're running out of memory?
> "ERROR: Out of Memory" is what I meant when I said I was running out of
> memory! :-) This is returned by psql, but it is the postmaster process that
> is hitting the wal
On Sunday, March 08, 2009, Gregory Stark wrote:
> Carl Sopchak writes:
> > Well, the upgrade to 8.3 seemed to rid me of the command limit, but now
> > I'm running out of memory. I have 2Gb physical and 8Gb swap (after
> > adding 4Gb).
>
> What do you mean you're running out of memory? For most pa
Carl Sopchak wrote:
> Well, the upgrade to 8.3 seemed to rid me of the command limit, but now I'm
> running out of memory. I have 2Gb physical and 8Gb swap (after adding 4Gb).
Do you have AFTER triggers on the involved tables? They are recorded on
memory and we have no mechanism to spill to dis
Carl Sopchak writes:
> Well, the upgrade to 8.3 seemed to rid me of the command limit, but now I'm
> running out of memory. I have 2Gb physical and 8Gb swap (after adding 4Gb).
What do you mean you're running out of memory? For most part of Postgres
that's only a problem if you've configured i
Well, the upgrade to 8.3 seemed to rid me of the command limit, but now I'm
running out of memory. I have 2Gb physical and 8Gb swap (after adding 4Gb).
Is there a way for me to run this outside of one huge transaction? This
really shouldn't be using more than a few hundred megs of RAM (assumin
Carl Sopchak writes:
> I have written a PL/pgSQL function that performs these calculations by
> reading
> the needed data, calculating, and saving the results. When run over a
> smaller set of data, it works fine. But when I tried to run it over this
> larger set of data, I got the error mes
11 matches
Mail list logo
