From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Vincent Dautremont <vincent(at)searidgetech(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: out of memory error |
Date: | 2012-05-22 20:04:55 |
Message-ID: | 7269.1337717095@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Vincent Dautremont <vincent(at)searidgetech(dot)com> writes:
>> An entirely blue-sky guess as
>> to what your code might be doing to trigger such a problem is if you
>> were constantly replacing the same function's definition via CREATE OR
>> REPLACE FUNCTION.
> Do you mean that what would happen is that when we call the plpgsql
> function, it executes each time a create or replace, then execute the
> function ?
> because my functions are all written like that :
> -- Function: spzoneinsert(integer, integer)
>> CREATE OR REPLACE FUNCTION spzoneinsert(i_zoneid integer, i_output_port
>> integer)
>> RETURNS void AS
Well, yeah, that is the common way to define a function. The question
was about whether you are constantly re-executing this same SQL
thousands of times over the course of a session. I think it would take
actually using the function in between such redefinitions to provoke a
plan leak, but if you were doing that it might explain the problem.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Vincent Dautremont | 2012-05-23 14:06:00 | Re: out of memory error |
Previous Message | Vincent Dautremont | 2012-05-22 19:46:41 | Re: out of memory error |