Re: [GENERAL] massive memory allocation until machine crashes

2007-02-22 Thread Alexander Elgert
Hello, thank you for the information, but it seems my messages are hold for moderator approval. A few of them seems to be dropped - I don't know. Richard Huxton schrieb: Alexander Elgert wrote: Hello, given is a postgres database in version --

Re: [GENERAL] massive memory allocation until machine crashes

2007-02-21 Thread Martijn van Oosterhout
On Wed, Feb 21, 2007 at 08:35:40PM +0100, Alexander Elgert wrote: > Yes, there are five FOREIGN keys in this table: There's your problem. You've got a trigger set to run after every delete, and you've got them set to wait until the end of the transaction. So postgres has to delete all the tuples

Re: [GENERAL] massive memory allocation until machine crashes

2007-02-21 Thread Alexander Elgert
Hello. Richard Huxton schrieb: Alexander Elgert wrote: Hello, given is a postgres database in version PostgreSQL 7.4.8 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.2 Upgrade to 7.4.16 as soon as is convenient - y

Re: [GENERAL] massive memory allocation until machine crashes

2007-02-15 Thread Richard Huxton
Alexander Elgert wrote: Hello, given is a postgres database in version PostgreSQL 7.4.8 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.2 Upgrade to 7.4.16 as soon as is convenient - you're missing 8 sets of bug-fixe

[GENERAL] massive memory allocation until machine crashes

2007-02-15 Thread Alexander Elgert
Hello, given is a postgres database in version PostgreSQL 7.4.8 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.2 and there is a table "visit" with 26 million tuples using 8 GB of space SELECT relname, reltuples, relpa