pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Kyle Cordes <kyle@kylecordes.com>
To: pgsql-performance@postgresql.org
Subject: Re: Overriding the optimizer
Date: Fri, 16 Dec 2005 19:42:30 -0600
Message-ID: <43A36D06.3090804@kylecordes.com> (raw)
In-Reply-To: <c2d9e70e0512160645q20ca27b7ja2f1235bed797747@mail.gmail.com>
References: <200512141603.52583.blargity@gmail.com>
	<1134629567.14248.27.camel@firebolt>
	<200512150148.16125.blargity@gmail.com>
	<1134644526.14248.60.camel@firebolt>
	<43A1C40D.8040006@paradise.net.nz>
	<43A1F6DB.3080805@modgraph-usa.com>
	<43A226E7.7040508@paradise.net.nz>
	<43A22BE3.6020103@modgraph-usa.com>
	<20051216052025.GB691@filer>
	<43A2CCEF.9030605@kylecordes.com>
	<c2d9e70e0512160645q20ca27b7ja2f1235bed797747@mail.gmail.com>

Jaime Casanova wrote:

>>What I would
>>really like is for my DBMS to give me a little more pushback - I'd like
>>to ask it to run a query, and have it either find a "good" way to run
>>the query, or politely refuse to run it at all.
>>    
>>

>set statement_timeout in postgresql.conf
>  
>

That is what I am doing now, and it is much better than nothing.

But it's not really sufficient, in that it is still quite possible for 
users repeatedly trying an operation that unexpectedly causes excessive 
DB usage, to load down the system to the point of failure.  In other 
words, I'd ideally like it to give up right away, not after N seconds of 
table scanning my 100-million-row tables... and not with a timeout, but 
with an explicit throwing up of its hands, exasperated, that it could 
not come up with an efficient way to run my query.

Kyle Cordes
www.kylecordes.com





view thread (41+ messages)  latest in thread

Message-ID: <43A36D06.3090804@kylecordes.com>
Permalink:  ../43A36D06.3090804@kylecordes.com/
Also on:    postgresql.org/message-id/43A36D06.3090804@kylecordes.com

 · 

reply
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-performance@postgresql.org
  Cc: kyle@kylecordes.com
  Subject: Re: Overriding the optimizer
  In-Reply-To: <43A36D06.3090804@kylecordes.com>

* 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