| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>, "Andy Colson" <andy(at)squeakycode(dot)net> |
| Subject: | Re: unlogged tables |
| Date: | 2010-12-08 17:14:08 |
| Message-ID: | 17066.1291828448@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Simon Riggs <simon(at)2ndquadrant(dot)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.
>> so maybe we should reconsider.
> +1 for choosing terminology without known conflicts with other
> significant products.
Yeah. Given this info I'm strongly inclined to stick with UNLOGGED.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Bunce | 2010-12-08 17:14:31 | Re: Optimize PL/Perl function argument passing [PATCH] |
| Previous Message | Robert Haas | 2010-12-08 17:09:42 | Re: Solving sudoku using SQL |