Re: UNLOGGED tables in psql \d

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>
Cc: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: UNLOGGED tables in psql \d
Date: 2011-02-22 13:19:58
Message-ID: AANLkTi=QEQ8pZAR3-HxKpbb7yRa49TAYWrrVWfeEcwM_@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 22, 2011 at 8:03 AM, Cédric Villemain
<cedric(dot)villemain(dot)debian(at)gmail(dot)com> wrote:
> The fact that you didn''t saw it might be enough to reconsider the way
> we display the unlogged state (and temp state) of a relation.
>
> Maybe some a "Durability: normal, temp, unlogged"  line at bottom of
> the \d output  ?

The term we use internally is "persistence", but I'm not really sure
it's worth making the \d output longer. In fact I'd much rather find
some way of going the other direction. Note also that the temp-ness
of a table can already be inferred from the schema.

Another thought is that we might eventually have global temporary
tables, where the schema is globally visible (like a permanent or
unlogged table) but each backend sees only its own contents. So
whatever we come up with here should generalize to that case as well.

Still another point is that "temp" can apply to any object type, but
"unlogged" can only apply to tables, indexes, and sequences. (We
don't currently implement it for sequences, though.)

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message rsmogura 2011-02-22 13:36:11 Re: Void binary patch
Previous Message Robert Haas 2011-02-22 13:16:08 Re: CopyReadLineText optimization revisited