pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Neil Conway <neilc@samurai.com>
To: shridhar@frodo.hserus.net
Cc: Saleem Burhani Baloch <peseek@khi.wol.net.pk>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow response of PostgreSQL
Date: Fri, 20 Feb 2004 09:34:31 -0500
Message-ID: <87d689es5k.fsf@mailbox.samurai.com> (raw)
In-Reply-To: <200402191456.19032.shridhar@frodo.hserus.net>
References: <200402190901.i1J91KY07596@ns2.khi.wol.net.pk>
	<200402191456.19032.shridhar@frodo.hserus.net>

Shridhar Daithankar <shridhar@frodo.hserus.net> writes:
> Right now, it is hotly debated on HACKERS about adding a NOWAIT
> clause to SELECT FOR UPDATE. If you think your application
> deployment is away for months and can try CVS head, you can expect
> some action on it in coming few days.

You can also try using the statement_timeout configuration variable
that is already included with 7.4. It's not exactly "don't wait for
locks", but should approximate that behavior well enough.

http://www.postgresql.org/docs/7.4/static/runtime-config.html#RUNTIME-CONFIG-CLIENT

-Neil




view thread (18+ messages)

Message-ID: <87d689es5k.fsf@mailbox.samurai.com>
Permalink:  ../87d689es5k.fsf@mailbox.samurai.com/
Also on:    postgresql.org/message-id/87d689es5k.fsf@mailbox.samurai.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: neilc@samurai.com, shridhar@frodo.hserus.net, peseek@khi.wol.net.pk
  Subject: Re: Slow response of PostgreSQL
  In-Reply-To: <87d689es5k.fsf@mailbox.samurai.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