From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | statement_cost_limit |
Date: | 2006-03-01 15:48:05 |
Message-ID: | 1141228085.27729.343.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2006-02-21 at 11:45 +1300, Mark Kirkwood wrote:
> Simon Riggs wrote:
> > A new parameter that allows the administrator to place sensible limits
> > on the size of queries executed.
> >
> > This is useful for ad-hoc SQL access
> > - when a very large table cannot realistically be sorted etc, so
> > prevents general users from saying "SELECT * FROM TABLE ORDER BY 1"
> >
> > - for preventing poorly coded SQL with missing join conditions from
> > causing impossibly huge cartesian joins which can tie up an important
> > production system for the weekend etc..
> >
> > Use EXPLAIN to find out what to set this to.
> >
> > Generally useful?
>
> Yes, sure does look useful to me!
e.g. statement_cost_limit = 10000000
This patch was discussed briefly on bizgres-general and is now being
submitted for discussion on main -hackers list.
Best Regards, Simon Riggs
Attachment | Content-Type | Size |
---|---|---|
statement_cost_limit.patch | text/x-patch | 2.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-01 16:03:12 | Re: Reg:lo_open error..pls help me |
Previous Message | Tom Lane | 2006-03-01 15:46:05 | Re: ipcclean in 8.1 broken? |