From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Eric E <whalesuit(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Preventing or controlling runaway queries |
Date: | 2005-12-05 19:35:45 |
Message-ID: | 1744.1133811345@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
Eric E <whalesuit(at)gmail(dot)com> writes:
> I've recently had a couple worrisome experiences with runaway
> queries in postgres 7.4 and 8.0, and I'm wondering what I can do to
> control or prevent these. When I ran a query against a large table, I
> accidentally omitted mistyped a table name, and a table was
> automatically added, resulting in a massive result set that crash my
> postmaster instance.
If it crashed your backend (as opposed to your client), we'd like to
see more details.
> Is there some way to limit the amount of
> memory a single query process can use?
See ulimit.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2005-12-05 19:38:39 | Re: EXPLAIN SELECT .. does not return |
Previous Message | David Link | 2005-12-05 19:17:16 | EXPLAIN SELECT .. does not return |
From | Date | Subject | |
---|---|---|---|
Next Message | Eric E | 2005-12-05 20:12:39 | Re: Preventing or controlling runaway queries |
Previous Message | Michael Burke | 2005-12-05 19:06:58 | Database with "override" tables |