Re: [HACKERS] [PATCHES] Patch(es) to expose n_live_tuples and
Joshua D. Drake wrote: The current terminology of live and dead is already used in many places in the documentation and in userspace; mostly around the need for maintainance of dead tuples within tables, reindex cleaning up dead pages, and even in the vacuum commands output (n dead tuples cannot be removed yet). Given this patch came from userland, istm people are comfortable enough with this terminology there is no need to change it. +1 OK. I will adjust any places that still use expired, and put the patch into the queue. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] [PATCHES] Patch(es) to expose n_live_tuples and
Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Alvaro Herrera wrote: I'm not really convinced that Bruce's proposed names seem any better to me. What's wrong with dead and live? In my mind, visible really means visible to anyone, and expired means visible to no one. Um ... surely, visibility is in the eye of the beholder (no smiley). I don't have an immediate suggestion for better terminology, but IMHO the whole point of visible/invisible terminology is that it depends on who's looking. Dead and live seem to convey a more appropriate air of finality. Expired is OK as a synonym for dead, but there is no thesaurus anywhere in the world that will suggest it as an antonym for visible. OK, so we need new terminology and we need it to be used consistenly in our documentation, whatever we choose. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] [PATCHES] Patch(es) to expose n_live_tuples and
On Tuesday 26 December 2006 23:12, Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Alvaro Herrera wrote:
I'm not really convinced that Bruce's proposed names seem any better
to me. What's wrong with dead and live?
In my mind, visible really means visible to anyone, and expired means
visible to no one.
Um ... surely, visibility is in the eye of the beholder (no smiley).
I don't have an immediate suggestion for better terminology, but IMHO
the whole point of visible/invisible terminology is that it depends on
who's looking. Dead and live seem to convey a more appropriate air
of finality.
Expired is OK as a synonym for dead, but there is no thesaurus
anywhere in the world that will suggest it as an antonym for visible.
OK, so we need new terminology and we need it to be used consistenly in
our documentation, whatever we choose.
The current terminology of live and dead is already used in many places in the
documentation and in userspace; mostly around the need for maintainance of
dead tuples within tables, reindex cleaning up dead pages, and even in the
vacuum commands output (n dead tuples cannot be removed yet). Given this
patch came from userland, istm people are comfortable enough with this
terminology there is no need to change it.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
Re: [HACKERS] [PATCHES] Patch(es) to expose n_live_tuples and
The current terminology of live and dead is already used in many places in the documentation and in userspace; mostly around the need for maintainance of dead tuples within tables, reindex cleaning up dead pages, and even in the vacuum commands output (n dead tuples cannot be removed yet). Given this patch came from userland, istm people are comfortable enough with this terminology there is no need to change it. +1 -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
