Re: unlogged tables - Mailing list pgsql-hackers

From Chris Browne
Subject Re: unlogged tables
Date
Msg-id 87ei9snm9z.fsf@cbbrowne.afilias-int.info
Whole thread Raw
In response to unlogged tables  (Andy Colson <andy@squeakycode.net>)
Responses Re: unlogged tables  (Robert Haas <robertmhaas@gmail.com>)
Re: unlogged tables  (Kineticode Billing <david@kineticode.com>)
List pgsql-hackers
tgl@sss.pgh.pa.us (Tom Lane) writes:
> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>> Robert Haas <robertmhaas@gmail.com> wrote:
>>> Simon Riggs <simon@2ndquadrant.com> wrote:
>>>> Note that DB2 uses the table modifier VOLATILE to indicate a
>>>> table that has a widely fluctuating table size, for example a
>>>> queue table.
>  
>>> the fact that DB2 uses that word to mean something entirely
>>> different is certainly a bit awkward
>  
>> It would be especially awkward should someone port their DB2
>> database to PostgreSQL without noticing the semantic difference, and
>> then find their data missing.
>
> Not to mention that DB2 syntax tends to appear in the standard a few
> years later.

And the term "volatile" has well-understood connotations that are
analagous to those in DB2 in the C language and various descendants.
<http://en.wikipedia.org/wiki/Volatile_variable>

I'm not sure "UNLOGGED" is perfect... If "TEMPORARY" weren't already
taken, it would be pretty good.

Other possibilities include TRANSIENT, EPHEMERAL, TRANSIENT, TENUOUS.

FLASH would be an amusing choice.  "PostgreSQL 9.1, now with support for
FLASH!"
-- 
output = ("cbbrowne" "@" "acm.org")
http://linuxdatabases.info/info/internet.html
I've told you for the fifty-thousandth time, stop exaggerating. 


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Review: Extensions Patch
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Optimize commit_siblings in two ways to improve group commit.