Hi Merlin, hi Alban,
thank you both for your helpful answers. Now, I splitted the function
into smaller parts which have to be called seperately one after another.
Probably, I will write a script for calling all the functions needed.
Not as nice as an all in one function, but if there is no other
On Thu, Apr 1, 2010 at 6:22 AM, Birgit Laggner
wrote:
> Dear list,
>
> I have some data (big size) and I've written a long function in pl/pgsql
> which processes the data in several steps. At a test run my function
> aborted because of memory exhaustion. My guess is, that everything what
> happens
On 1 Apr 2010, at 14:38, Birgit Laggner wrote:
> Hi Alban,
>
> thanks for your detailed answer!
>
> My database settings:
> max connections: 20
> work_mem: 100MB
> shared buffers: 12000MB
>
> Server memory:
> physical 32GB
> total memory 50GB (incl. swap)
> shared memory ??
Ok, so max work_mem
Hi Alban,
thanks for your detailed answer!
My database settings:
max connections: 20
work_mem: 100MB
shared buffers: 12000MB
Server memory:
physical 32GB
total memory 50GB (incl. swap)
shared memory ??
I am not sure if I use deferred constraints - the only constraints I use
in the function are
On 1 Apr 2010, at 12:22, Birgit Laggner wrote:
> Dear list,
>
> I have some data (big size) and I've written a long function in pl/pgsql
> which processes the data in several steps. At a test run my function
> aborted because of memory exhaustion. My guess is, that everything what
> happens durin
2010/4/1 Birgit Laggner
> Hi Grzegorz,
>
> sorry, but that doesn't help me, perhaps you could get a little bit
> clearer:
>
> @a) Does the use of SAVEPOINT avoid memory overflow? I could not find an
> explanation about memory use in the documentation of SAVEPOINT.
>
> transactions don't really us
Hi Grzegorz,
sorry, but that doesn't help me, perhaps you could get a little bit clearer:
@a) Does the use of SAVEPOINT avoid memory overflow? I could not find an
explanation about memory use in the documentation of SAVEPOINT.
@b) Do you mean I should not process my data or I should not use plpg
2010/4/1 Birgit Laggner :
> Dear list,
>
> I have some data (big size) and I've written a long function in pl/pgsql
> which processes the data in several steps. At a test run my function
> aborted because of memory exhaustion. My guess is, that everything what
> happens during the function transact
a) you can't explicitly control transactions in plpgsql. If you need some
sort of a form of it, use save points.
b) you are trying to outsmart database software, and this is just a biiig
mistake, and you should stop doing that completely.
Dear list,
I have some data (big size) and I've written a long function in pl/pgsql
which processes the data in several steps. At a test run my function
aborted because of memory exhaustion. My guess is, that everything what
happens during the function transaction is stored in the memory - until
i
10 matches
Mail list logo
