> What would be interesting would be to name part of the project
> 'Postgres'. Right now the database superuser is 'postgres', and no one
> seems to be confused by that. I think we have enough people who like
> both names that we should be able to come up with a compromise that
> everyone likes. I am not sure what parts of the project we could name
> "Postgres" instead of "PostgreSQL".
FWIW, I'm considering doing a lot of the shilling for 9.0 as "Postgres
9". It looks better on a t-shirt design. So I fully support exploiting
the alias. I just think that a change of the official name of the
project is too much trouble and does not provide clear marketing gains
the way, say, doing more case studies would.
Currently it appears that Greg is the only one who really cares about a
name change; other people seem to be OK with the whole "official
nickname" concept. So, time to drop this again I think. Greg can bring
it up again for 10.0. ;-)
--Josh
