From: Tom Lane <tgl@sss.pgh.pa.us>
To: Eric E <whalesuit@gmail.com>
Cc: pgsql-general@postgresql.org
Subject: Re: Preventing or controlling runaway queries
Date: Mon, 05 Dec 2005 14:35:45 -0500
Message-ID: <1744.1133811345@sss.pgh.pa.us> (raw)
In-Reply-To: <43948EC3.4030407@gmail.com>
References: <43948EC3.4030407@gmail.com>
Eric E <whalesuit@gmail.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, whalesuit@gmail.com, pgsql-general@postgresql.org
Subject: Re: Preventing or controlling runaway queries
In-Reply-To: <1744.1133811345@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox