Re: LockAcquire: lock table 1 is out of memory

I raised the parameter to 256 and the process finished. Thank you Tom. Does raising that parameter cause the database to slow down? The process ended up taking 14.5 hours to finish! That seems like a long long time.

Also, do you think that the use of a temporary table inside an inner loop, being created and dropped over and over again could have caused the problem in the beginning?

Thank you,
Betsy Barker

On Mon, 13 Sep 2004 10:47:55 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Betsy Barker <betsy(dot)barker(at)supportservicesinc(dot)com> writes:
> > I am getting the following error while running a series of stored procedures. I have increased the max_locks_per_transaction
> > parameter from 64 (the default) to 128 and I still received this
> > error. Can anyone tell me waht else I could do?
>
> Raise it further ...
>
> Note also that you need a postmaster restart (not just SIGHUP) to make
> the increase take effect.
>
> regards, tom lane
>

--
Betsy Barker
IT Manager
Support Services, Inc
(720)489-1630 X 38