Re: Buglist

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Vivek Khera <khera(at)kcilink(dot)com>
Cc: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: Buglist
Date: 2003-08-20 13:20:59
Message-ID: 20030820132059.GA5221@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Tue, Aug 19, 2003 at 21:51:14 -0400,
Vivek Khera <khera(at)kcilink(dot)com> wrote:
>
> I'm not promoting any change in the MVCC. What I'm saying is that it
> would be really cool if the backend process itself could recognize
> that a row is no longer referenced by any transactions upon
> termination of the transaction, and release it back to the system.
> This is just what vacuum does but in a batched manner. I would love
> to see it incremental. This would result in pretty much near zero
> internal fragmentation, I think.

Why do you care about about the details of the implementation (rather than
the performance)? If it were faster to do it that way, that's how it would
have been done in the first place. The cost of doing the above is almost
certainly going to be an overall performance loser.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vasili G. Yanov 2003-08-20 13:21:55 uptime problem
Previous Message Robert Treat 2003-08-20 12:59:14 Re: Mail server load

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2003-08-20 14:55:50 Re: Buglist
Previous Message segfault 2003-08-20 10:15:22 Your details