Skip site navigation (1) Skip section navigation (2)

Re: Patch(es) to expose n_live_tuples and

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Glen Parker <glenebob(at)nwlink(dot)com>, Postgresql Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Patch(es) to expose n_live_tuples and
Date: 2006-12-27 03:33:14
Message-ID: 200612270333.kBR3XER18525@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Alvaro Herrera wrote:
> Glen Parker wrote:
> 
> [slightly reformatted for sanity]
> 
> > Bruce Momjian wrote:
> > >Is this something we want in 8.3?  I am thinking visible/expired would
> > >be clearer terms.
> >
> > I'd love to see this back patched into 8.2.1 if possible.
> > 
> > Should I resubmit with new names?
> 
> I'm not really convinced that Bruce's proposed names seem any better to
> me.  What's wrong with "dead" and "live"?

With MVCC, my thought has always been that alive/dead is in the eye of
the beholder/backend.  For column names the user will see, I think we
need to use terms that we have used in the past.  If we want to move to
alive/dead, fine, but we then need to make sure we use consistent terms
in the documentation.

In my mind, visible really means "visible to anyone", and expired means
visible to no one.  I don't think live/dead can be as clear as
visible/expired, e.g. saying the tuple is "live to someone" seems
more awkward.

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

  + If your life is a hard drive, Christ can be your backup. +

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-12-27 03:43:27
Subject: Re: Patch(es) to expose n_live_tuples and
Previous:From: Andrew DunstanDate: 2006-12-27 03:24:39
Subject: Re: Patch(es) to expose n_live_tuples and

pgsql-patches by date

Next:From: Tom LaneDate: 2006-12-27 03:43:27
Subject: Re: Patch(es) to expose n_live_tuples and
Previous:From: Andrew DunstanDate: 2006-12-27 03:24:39
Subject: Re: Patch(es) to expose n_live_tuples and

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group