Search Postgresql Archives

Re: how to avoid that a postgres session eats up all the memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Clemens Schwaighofer <clemens.schwaighofer@xxxxxxxxxx>
Subject: Re: how to avoid that a postgres session eats up all the memory
From: Grzegorz Jaśkiewicz <gryzman@xxxxxxxxx>
Date: Fri, 23 Jan 2009 09:48:42 +0000
Cc: Richard Huxton <dev@xxxxxxxxxxxx>, pgsql-general@xxxxxxxxxxxxxx
In-reply-to: <4979080B.30408@xxxxxxxxxx>

try raising work_mem before the delete; on single connection :

set work_mem=512000; DELETE FROM ......;

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: how to avoid that a postgres session eats up all the memory
  - From: Schwaighofer Clemens

References:
- how to avoid that a postgres session eats up all the memory
  - From: Clemens Schwaighofer
- Re: how to avoid that a postgres session eats up all the memory
  - From: Richard Huxton
- Re: how to avoid that a postgres session eats up all the memory
  - From: Grzegorz Jaśkiewicz
- Re: how to avoid that a postgres session eats up all the memory
  - From: Clemens Schwaighofer

Prev by Date: Re: Segmentation fault in backend/access/heap/pruneheap.c: heap_page_prune_opt() calling PageIsPrunable () with NULL page on FreeBSD / PowerPC
Next by Date: Re: how to avoid that a postgres session eats up all the memory
Previous by thread: Re: how to avoid that a postgres session eats up all the memory
Next by thread: Re: how to avoid that a postgres session eats up all the memory
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]