Excerpts from Joshua D. Drake's message of mié jun 22 15:37:17 -0400 2011:
> It seems we did come up with a use case in the procpid discussion. The
> ability to change the names of columns/databases etc, to handle the
> fixing of bad decision decisions during development over time.
Let's start with what was discussed and supported in that thread, that
is, databases. It seems less clear that columns are widely believed to
be a good idea to have synonyms for. Besides, synonyms for databases
should be reasonably simple to implement, which is not something I would
say for columns.
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
In response to
pgsql-hackers by date
|Next:||From: Greg Stark||Date: 2011-06-22 23:37:24|
|Subject: Re: Coding style point: "const" in function parameter declarations|
|Previous:||From: Kevin Grittner||Date: 2011-06-22 22:08:40|
|Subject: Re: Repeated PredicateLockRelation calls during seqscan|