From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | David E(dot) Wheeler <david(at)kineticode(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_class.relistemp |
Date: | 2011-07-13 19:38:43 |
Message-ID: | 1310585855-sup-388@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Bruce Momjian's message of mié jul 13 15:24:35 -0400 2011:
> David E. Wheeler wrote:
> > On Jul 13, 2011, at 12:14 PM, Bruce Momjian wrote:
> >
> > >> I'm wondering if it would be possible to restore the relistemp column
> > >> to pg_class, at least for backwards compatibility, so that apps that
> > >> expected it can continue to work on both 9.0 and 9.1. Even if it's
> > >> read-only somehow, and the same as `relpersistence <> 't'`.
> > >
> > > Uh, that is going to require an initdb, and it is unlinkely we are going
> > > to need that this far into 9.1 beta.
> >
> > I was afraid of that.
> >
> > > Also, we don't normally keep
> > > system table columns around for backward compatibility because of the
> > > confusion it can cause, e.g. which column do I look at?
> >
> > The one that's documented.
>
> 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).
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2011-07-13 19:48:38 | Re: pg_class.relistemp |
Previous Message | Bruce Momjian | 2011-07-13 19:24:35 | Re: pg_class.relistemp |