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

2009-03-26 Thread Dhaval Jaiswal
r_id where you given appropriate condition. --- Thanks & Regards Dhaval Jaiswal EnterpriseDB www.enterprisedb.com   From: Clemens Schwaighofer To: pgsql-general@postgresql.org Sent: Thursday, January 22, 2009 2:21:47 PM Subject: [GENERAL] how to avoid that

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

2009-01-25 Thread Clemens Schwaighofer
On 01/24/2009 12:42 AM, Richard Huxton wrote: > Clemens Schwaighofer wrote: >> On 01/22/2009 07:11 PM, Richard Huxton wrote: >>> Clemens Schwaighofer wrote: Hi, I just literally trashed my test server with one delete statement because the psql used up all its memory and started

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

2009-01-23 Thread Richard Huxton
Clemens Schwaighofer wrote: > On 01/22/2009 07:11 PM, Richard Huxton wrote: >> Clemens Schwaighofer wrote: >>> Hi, >>> >>> I just literally trashed my test server with one delete statement >>> because the psql used up all its memory and started to swap like crazy. >>> >>> my delete looked like this

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

2009-01-23 Thread Schwaighofer Clemens
But if I have my work mem small, shouldn't it then just end with "out of memory" and not use up all the memory ... On Fri, Jan 23, 2009 at 18:48, Grzegorz Jaśkiewicz wrote: > try raising work_mem before the delete; on single connection : > > set work_mem=512000; DELETE FROM ..; > -- [ Cle

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

2009-01-23 Thread Grzegorz Jaśkiewicz
try raising work_mem before the delete; on single connection : set work_mem=512000; DELETE FROM ..; -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

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

2009-01-22 Thread Clemens Schwaighofer
On 01/22/2009 07:19 PM, Grzegorz Jaśkiewicz wrote: > try making it in two steps,using temp table maybe. > how many rows does the subselect generate ? the subselect returns 57.000 rows. -- [ Clemens Schwaighofer -=:~ ] [ IT Engineer/Web Producer/Planning/Manager

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

2009-01-22 Thread Clemens Schwaighofer
On 01/22/2009 07:11 PM, Richard Huxton wrote: > Clemens Schwaighofer wrote: >> Hi, >> >> I just literally trashed my test server with one delete statement >> because the psql used up all its memory and started to swap like crazy. >> >> my delete looked like this >> >> DELETE FROM table_foo WHERE ba

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

2009-01-22 Thread Grzegorz Jaśkiewicz
try making it in two steps,using temp table maybe. how many rows does the subselect generate ? -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

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

2009-01-22 Thread Richard Huxton
Clemens Schwaighofer wrote: > Hi, > > I just literally trashed my test server with one delete statement > because the psql used up all its memory and started to swap like crazy. > > my delete looked like this > > DELETE FROM table_foo WHERE bar_id IN (SELECT DISTINCT bar_id FROM bar > LEFT JOIN

[GENERAL] how to avoid that a postgres session eats up all the memory

2009-01-22 Thread Clemens Schwaighofer
Hi, I just literally trashed my test server with one delete statement because the psql used up all its memory and started to swap like crazy. my delete looked like this DELETE FROM table_foo WHERE bar_id IN (SELECT DISTINCT bar_id FROM bar LEFT JOIN ... LEFT JOIN ... LEFT JOIN WHERE table.