Re: Prepping to break every past release...

From: decibel <decibel(at)decibel(dot)org>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Prepping to break every past release...
Date: 2009-03-14 14:07:37
Message-ID: DA8FADF8-D8D0-440B-8A54-60655E345A22@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mar 4, 2009, at 5:07 PM, Josh Berkus wrote:
>> Back on that track, I'd like to see a facility whereby we could
>> provide an alias (or synonym, to use a nearby subject) columns and
>> other objects. That would help to overcome naming glitches without
>> breaking things quite so much.
>
> Believe it or not, a large PostgreSQL user in LA just buttonholed
> me about that particular feature idea at SCALE. So it might be
> generally useful as well -- not just for the system catalogs, bug
> to allow businesses with long-use databases to manage change over
> time.

Yes, I think aliasing (especially at the table level) would be handy.

And +1 on reviving newsysviews, but of course I'm biased... ;P
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message decibel 2009-03-14 14:19:40 Re: hstore improvements?
Previous Message Martijn van Oosterhout 2009-03-14 12:53:57 Re: Has anybody think about changing BLCKSZ to an option of initdb?