Re: two memory-consuming postgres processes

>>> Alexy Khrabrov wrote:

> SInce I don't index on that
> new column, I'd assume my old indices would do -- do they change
> because of rows deletions/insertions, with the effective new rows
> addresses?

Every update is a delete and insert.  The new version of the row must
be added to the index.  Every access through the index then has to
look at both versions of the row to see which one is "current" for its
transaction.  Vacuum will make the space used by the dead rows
available for reuse, as well as removing the old index entries and
making that space available for new index entries.

-Kevin