Re: Nested loop in simple query taking long time

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com>
Cc: Henrik <henke(at)mac(dot)se>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Nested loop in simple query taking long time
Date: 2007-12-06 21:18:30
Message-ID: 20071206211830.GL8451@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Gauthier, Dave wrote:
> Future Enhancement?
> If the column's new value can fit in the space already being used by the
> existing value, just change the column value in place and leave the
> record alone. Would reduce the need for vacuum in many cases.

That's in 8.3. Not exactly like that (because it doesn't work in
Postgres due to MVCC), but something close. Look for HOT in release
notes.

--
Alvaro Herrera Valdivia, Chile ICBM: S 39º 49' 18.1", W 73º 13' 56.4"
Syntax error: function hell() needs an argument.
Please choose what hell you want to involve.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John Wells 2007-12-06 21:23:47 Determining current block size?
Previous Message Ted Byers 2007-12-06 21:16:53 Re: SQL design pattern for a delta trigger?