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: Richard Huxton <dev@xxxxxxxxxxxx>
Subject: Re: how to avoid that a postgres session eats up all the memory
From: Grzegorz Jaśkiewicz <gryzman@xxxxxxxxx>
Date: Thu, 22 Jan 2009 10:19:25 +0000
Cc: Clemens Schwaighofer <clemens.schwaighofer@xxxxxxxxxx>, pgsql-general@xxxxxxxxxxxxxx
In-reply-to: <4978466A.5030407@xxxxxxxxxxxx>

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@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: Clemens Schwaighofer

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

Prev by Date: Re: how to avoid that a postgres session eats up all the memory
Next by Date: Re: [Plproxy-users] A complex plproxy query
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]

Powered by Linux