Re: two memory-consuming postgres processes

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Alexy Khrabrov" <deliverable(at)gmail(dot)com>, "Greg Smith" <gsmith(at)gregsmith(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: two memory-consuming postgres processes
Date: 2008-05-02 21:43:58
Message-ID: 481B44AF.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>>> 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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alexy Khrabrov 2008-05-02 22:03:12 Re: two memory-consuming postgres processes
Previous Message PFC 2008-05-02 21:30:44 Re: two memory-consuming postgres processes