[Nitro] Idea for improving performance
Reid.Thompson at ateb.com
Sat Nov 19 06:14:20 EST 2005
>>not sure whether it would make any difference for PostgreSQL -- If I
>>understand correctly, an update means a delete and insert regardless of
>>the number of fields you are updating. Seems like the only gain would
>>be size of the sql statement i.e. not very much.
>*Postgresql* deletes and inserts on an update? Are you sure?
>Nitro-general mailing list
>Nitro-general at rubyforge.org
yes, read 22.1.1. Recovering disk space from
http://www.postgresql.org/docs/8.1/interactive/maintenance.html -- and
search the postgresql mail lists.
an update 'marks' the original tuple for deletion, andinserts a new row
with the updated data ( it just does it very well and very fast ) :)
. That's why vacuum'ing is required --- and why it's being added as an
'auto' functionality in 8.1 see 22.1.4. The auto-vacuum daemon
More information about the Nitro-general