Re: Update comment for README.HOT

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Update comment for README.HOT
Date: 2010-09-17 21:23:28
Message-ID: 201009172123.o8HLNS716468@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > + This means that UPDATE, DELETE, and SELECT can trigger space
> > + reclamation, while INSERT ... VALUES cannot because it does not retrieve
> > + a row.
>
> I don't believe that's correct. It might have happened to work that way
> for you in a particular test. It's certainly not something I'd document
> as being intended long-term behavior.

Well, I would like to document something about this because I was
surprised that when INSERT did not trigger a cleanup. I realize we
might change the behavior but then we would update the file too,
hopefully.

How is the attached version using "often"? I also clarified it is < 10%
free.

I found this while doing tests for a new MVCC talk I will be delivering
at PG West.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

Attachment Content-Type Size
unknown_filename text/plain 847 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2010-09-17 21:34:28 Re: Report: removing the inconsistencies in our CVS->git conversion
Previous Message Tom Lane 2010-09-17 21:21:55 Re: Report: removing the inconsistencies in our CVS->git conversion