statement_cost_limit - Mailing list pgsql-hackers

From Simon Riggs
Subject statement_cost_limit
Date
Msg-id 1141228085.27729.343.camel@localhost.localdomain
Whole thread Raw
Responses Re: statement_cost_limit
List 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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ipcclean in 8.1 broken?
Next
From: Peter Eisentraut
Date:
Subject: Re: Automatic free space map filling