Re: Nested loop in simple query taking long time

6 dec 2007 kl. 22.18 skrev Alvaro Herrera:

> 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.
>
I want 8.3 now! =)

I did a test last night. Table grew from 16 kb to 648 kb. The index
grew from 64 kb to 6056 MB.
A REINDEX took the index back down to 64 kb. The good thing is that
REINDEX takes about 1 sek so I can do that quite often. :)

Thanks for all the input
Henke

> --
> 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.
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match