Re: pg_class.relistemp

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_class.relistemp
Date: 2011-07-13 19:48:38
Message-ID: 020329B5-9709-4AE1-87E2-4029C93D4D33@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jul 13, 2011, at 12:38 PM, Alvaro Herrera wrote:

>> Well, that assumes people read the documention and don't just do \d.
>> Keeping cruft around over time makes the system more complex.
>
> This seems a case where column synonyms would have been useful (as was
> the procpid / pid change).

Well it couldn't just be that, because the data type has changed, too. Unless you could make a kind of "view column" or something where the expression was `relpersistence <> 't'`.

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2011-07-13 19:57:41 Re: pg_class.relistemp
Previous Message Alvaro Herrera 2011-07-13 19:38:43 Re: pg_class.relistemp